<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Mar 9, 2016 at 3:59 PM Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com">gribozavr@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Mar 9, 2016 at 3:52 PM, Shawn Erickson <<a href="mailto:shawnce@gmail.com" target="_blank">shawnce@gmail.com</a>> wrote:<br>
> I see a handful of issues like the following coming about because of changes<br>
> to `Range`. In the past `Range` conformed to `Collection` so `count` came<br>
> from `Collection` which returned a type of `ForwardIndex.Distance` (e.g.<br>
> `_SignedInteger`). It now comes from `Strideable`’s `distance(to:)` which<br>
> returns `Strideable.Stride` (e.g. `SignedNumber`).<br>
<br>
Yeah, we had those. Try pulling from the branch, I have resolved some<br>
of these issues. I'll be working on HashedCollections next, feel free<br>
to take Flatten and FlatMap.<br></blockquote><div><br></div><div>Ah I see... should have thought of that fix, forest for the trees.</div><div><br></div><div>You also fixed some of the things I had fixed locally! :)</div><div><br></div><div>Will put aside my changes for all but Flatten at the moment.</div><div><br></div><div>Thanks,</div><div>-Shawn </div></div></div>