> On Jun 22, 2016, at 10:05 AM, Nate Cook <[email protected]> wrote:
> Pull Requests
> 
> Additive
> #346 Introducing with to the Standard Library         

Yeah, mea culpa -- but mea culpa with a reason. Method cascades are not going 
to be in 3. This is intentionally a stop-gap additive feature specifically for 
3, since it's so widely used in the dev community for both Swift constructs and 
Cocoa(touch) initialization. It's super easy-to-implement/add. If considered, 
it makes a lot of sense in the 3 timeframe. It makes less sense (although it's 
still useful) after 3.

> Additive
> #369 Conditional Compilation Blocks proposal          

Definitely additive but it's stuff again that's extremely practical and has a 
big demand, all the way back to the first moments of open source, and it's 
pretty much all implemented as private methods now. 

> Other
> #370 Renaming the OS X Platform Conditional Compilation Test: Doug Gregor 
> suggested this could just be implemented as a bug fix

I've put in the bug report. I tried implementing it myself, but apparently my 
compiler fu is not as strong as I hoped (although the errors in my patch seem 
to come from code I have absolutely nothing to do with -- I was thinking of 
throwing myself on Dmitri's mercy for that).

-- E
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to