> On Nov 29, 2017, at 9:21 AM, Wallacy via swift-evolution
> wrote:
>
> Distances, yes... Count, not necessarily.
It doesn’t really help you to have an extra bit of range for “count" that can’t
be expressed in the distance, i.e., where c.count returns a value but
c.distance(from: c.startIn
On Wed, Nov 29, 2017 at 10:46 AM, Ben Cohen wrote:
> You can argue the current status is a bug, but…
>
> Welcome to Apple Swift version 4.0.1 (swiftlang-900.0.67 clang-900.0.38).
> Type :help for assistance.
> 1> CountableRange.IndexDistance.self
> $R0: Int.Type = Int
> 2> (Int64.min.. Execut
Distances, yes... *Count*, not necessarily.
Em qua, 29 de nov de 2017 às 15:17, Xiaodi Wu
escreveu:
> Distance must be signed, so it cannot be UInt.
> On Wed, Nov 29, 2017 at 11:14 Wallacy wrote:
>
>> I think is that's why some folks ask for count be UInt (or UInt64 when
>> appropriate) some t
Distance must be signed, so it cannot be UInt.
On Wed, Nov 29, 2017 at 11:14 Wallacy wrote:
> I think is that's why some folks ask for count be UInt (or UInt64 when
> appropriate) some time ago.
>
> I dont know how solve this, but appear to be less painful than current
> IndexDistance.
>
> Em qua
I think is that's why some folks ask for count be UInt (or UInt64 when
appropriate) some time ago.
I dont know how solve this, but appear to be less painful than current
IndexDistance.
Em qua, 29 de nov de 2017 às 14:46, Ben Cohen via swift-evolution <
swift-evolution@swift.org> escreveu:
> You
You can argue the current status is a bug, but…
Welcome to Apple Swift version 4.0.1 (swiftlang-900.0.67 clang-900.0.38). Type
:help for assistance.
1> CountableRange.IndexDistance.self
$R0: Int.Type = Int
2> (Int64.min.. On Nov 29, 2017, at 4:04 AM, Xiaodi Wu wrote:
>
> So that we are all
So that we are all clear on the implications of this, if IndexDistance
becomes Int, ranges of integers will stop conforming to Collection, because
Int.min.. wrote:
> My suggestion would be: don’t have your Collection-like type conform to
> Collection. Give it collection-like methods if you want th
> On 28. Nov 2017, at 02:34, Douglas Gregor via swift-evolution
> wrote:
>
> Hello Swift community,
>
> The review of SE-0191 "Eliminate IndexDistance from Collection" begins now
> and runs through December 3, 2017. The proposal is available here:
>
> https://github.com/apple/swift-evolutio
+1. Feels more Swifty to keep things simple when additional complexity isn’t
warrented.
> Hello Swift community,
>
>
> The review of SE-0191 "Eliminate IndexDistance from Collection" begins now
> and runs through December 3, 2017. The proposal is available here:
>
> > https://github.com/apple
On Mon, Nov 27, 2017 at 5:34 PM Douglas Gregor via swift-evolution <
swift-evolution@swift.org> wrote:
> Hello Swift community,
>
> The review of SE-0191 "Eliminate IndexDistance from Collection" begins now
> and runs through December 3, 2017. The proposal is available here:
>
>
> https://github.c
Hi list,
> On 28. Nov 2017, at 02:34, Douglas Gregor via swift-evolution
> wrote:
>
> The review of SE-0191 "Eliminate IndexDistance from Collection" begins now
> and runs through December 3, 2017. The proposal is available here:
>
> • What is your evaluation of the proposal?
+1.
>
> On Nov 27, 2017, at 5:58 PM, Guillaume Lessard via swift-evolution
> wrote:
>
>
>
>> On Nov 27, 2017, at 18:34, Douglas Gregor via swift-evolution
>> wrote:
>>
>> Hello Swift community,
>>
>> The review of SE-0191 "Eliminate IndexDistance from Collection" begins now
>> and runs throug
My suggestion would be: don’t have your Collection-like type conform to
Collection. Give it collection-like methods if you want them, like an indexing
and slicing subscript that takes an Int64. It can still conform to Sequence.
In practice, these “huge” collections will be mostly used concretely
The proposal mentions one reasonable situation where a larger-than-Int type
would be useful, namely a Collection wrapping a memory-mapped file, being
used on 32-bit systems.
Is there a recommended migration strategy for this scenario?
Nevin
On Mon, Nov 27, 2017 at 8:34 PM, Douglas Gregor via sw
> On Nov 27, 2017, at 18:34, Douglas Gregor via swift-evolution
> wrote:
>
> Hello Swift community,
>
> The review of SE-0191 "Eliminate IndexDistance from Collection" begins now
> and runs through December 3, 2017.
[snip]
> • What is your evaluation of the proposal?
I approve heartily.
I
Hello Swift community,
The review of SE-0191 "Eliminate IndexDistance from Collection" begins now and
runs through December 3, 2017. The proposal is available here:
https://github.com/apple/swift-evolution/blob/master/proposals/0191-eliminate-indexdistance.md
Reviews are an important part of the
16 matches
Mail list logo