Ok, thanks!
On Wed, Jun 7, 2017 at 4:52 PM, Karl Wagner wrote:
>
> On 7. Jun 2017, at 11:29, Jens Persson via swift-users <
> swift-users@swift.org> wrote:
>
> I see, this quote from the introduction of SE-0142 is not to be taken
> literally then:
>
> For example, the SequenceType protocol could
thanks, guys! dp array should be var, not let, but the compile run too
slow. It indeed a bug. Optimizing the code for the compiling time is
really a headache for coders. I am using the Xcode 8.1. Hoping it can be
fixed in next release.
*best wishes for you *
2017-06-06 8:57 GMT+08:00 Geordi
> On Mar 20, 2017, at 11:39 AM, Jon Shier via swift-evolution
> wrote:
>
> So when is this transition happening? The sooner the better, as Mail
> can’t really handle threads with large messages, like the recent evolution
> threads about Foundation serialization and decoding. It just stop
> On 7. Jun 2017, at 11:29, Jens Persson via swift-users
> wrote:
>
> I see, this quote from the introduction of SE-0142 is not to be taken
> literally then:
>
> For example, the SequenceType protocol could be declared as follows if the
> current proposal was accepted:
>
> protocol Sequence
I see, this quote from the introduction of SE-0142 is not to be taken
literally then:
For example, the SequenceType protocol could be declared as follows if the
current proposal was accepted:
protocol Sequence {
associatedtype Iterator : IteratorProtocol
associatedtype SubSequence : Seque
> On Jun 7, 2017, at 12:46 AM, Jens Persson wrote:
>
> Ok, I thought it was part of SE-0142 (which has status "implemented (Swift
> 4)”.
That’s just the where clause part. There’s still plenty you can accomplish with
them even if they do not introduce recursive conformances :)
Slava
> /Jens
Ok, I thought it was part of SE-0142 (which has status "implemented (Swift
4)".
/Jens
On Wed, Jun 7, 2017 at 9:39 AM, Slava Pestov wrote:
> This is a rather complex feature that is not actually implemented in Swift
> 4 (or Swift 3 for that matter). Work is underway to support this, though.
> The
This is a rather complex feature that is not actually implemented in Swift 4
(or Swift 3 for that matter). Work is underway to support this, though. The
fact that the second example does not produce a diagnostic is a bug (probably
you will not be able to define a type that conforms to P2 anyway)
