Although there are historical architectures where the addressable space
exceeds the word size, IIUC, we'd be saying that collections don't support
more elements than there are addressable units in memory. Are there very
many use cases where a collection needs to have more elements than that? I
I guess I am mildly +1. I can’t think of a case where this wouldn’t be some
sort of Integer, but I am also open to arguments against. I am not sure what
the utility of having a type for this besides Int is...
Thanks,
Jon
> On Nov 8, 2017, at 1:37 PM, Ben Cohen via swift-evolution
>
+1 it seems like a generic type just for the sake of it. Many languages do
without a specific type for distance and use Int and it is a better solution
because it is simpler.
-- Howard.
> On 9 Nov 2017, at 8:37 am, Ben Cohen via swift-evolution
> wrote:
>
>
> Hi
> On Nov 8, 2017, at 1:55 PM, Ben Cohen wrote:
>
> Apologies to Nate Cook, from whom this important came.
I would love to pretend my accidentally a word there was a joke. But it wasn’t…
___
swift-evolution mailing list
> On Nov 8, 2017, at 1:37 PM, Ben Cohen via swift-evolution
> wrote:
>
> This turns any problem of writing a generic collection algorithm into both a
> collection _and_
> problem.
Gah, typo. That should read “This turns any problem of writing a generic
collection
Hi Swift Evolution,
A pitch for review, aimed at simplifying generic Collection algorithms.
Online copy here:
https://github.com/airspeedswift/swift-evolution/blob/5d1ffda2e83f5b95a88d5ce3948c5fd0d59622f4/proposals/-eliminate-indexdistance.md