Re: [swift-evolution] Pitch: Cross-module inlining and specialization

> On Oct 3, 2017, at 12:28 AM, Andrew Trick via swift-evolution > wrote: > > > >> On Oct 2, 2017, at 11:20 PM, Slava Pestov via swift-evolution >> mailto:swift-evolution@swift.org>> wrote: >> >> >>> On Oct 2, 2017, at 11:11 PM, Slava Pestov via swift-evolution >>> mailto:swift-evolution@s

Re: [swift-evolution] [Proposal] Foundation Swift Archival & Serialization

> On Mar 17, 2017, at 12:49 PM, Itai Ferber wrote: > > On 17 Mar 2017, at 12:18, Michael Gottesman wrote: > > > On Mar 16, 2017, at 10:23 AM, Joe Groff via swift-evolution > wrote: > > On Mar 16, 2017, at 10:21 AM, Itai Ferber wrote: > > On 15 Mar 2017, at 19:12, Joe Groff wrote: > > >

Re: [swift-evolution] [Proposal] Foundation Swift Archival & Serialization

> On Mar 16, 2017, at 10:23 AM, Joe Groff via swift-evolution > wrote: > > >> On Mar 16, 2017, at 10:21 AM, Itai Ferber wrote: >> >> On 15 Mar 2017, at 19:12, Joe Groff wrote: >> >> >> On Mar 15, 2017, at 6:46 PM, Itai Ferber wrote: >> >> Thanks Joe, and thanks for passing this along! >>

Re: [swift-evolution] associated objects

> On Sep 28, 2016, at 9:27 AM, Robert Widmann via swift-evolution > wrote: > > Have you got a significant use-case for this that absolutely can't be solved > by extensions or subclassing? > > This does have ABI impact but more concerning for me is the performance > impact and that the existi

Re: [swift-evolution] Should Swift apply "statement scope" for ARC

> On Sep 23, 2016, at 3:29 PM, John Holdsworth wrote: > > Sorry, I’m being a little slow on the uptake here. So in future optimised > Swift the > scope of a variable continuing an object doesn't determine it’s lifetime at > all! > That seems quite a departure. > > This means you have to be ve

Re: [swift-evolution] [Proposal] Normalize Unicode Identifiers

> On Sep 22, 2016, at 6:11 PM, Xiaodi Wu wrote: > > On Thu, Sep 22, 2016 at 7:44 PM, Michael Gottesman > wrote: > >> On Sep 22, 2016, at 5:09 PM, Xiaodi Wu > > wrote: >> >> On Thu, Sep 22, 2016 at 6:54 PM, Michael Gottesman >

Re: [swift-evolution] [Proposal] Normalize Unicode Identifiers

> On Sep 22, 2016, at 5:09 PM, Xiaodi Wu wrote: > > On Thu, Sep 22, 2016 at 6:54 PM, Michael Gottesman > wrote: > >> On Sep 22, 2016, at 4:19 PM, Xiaodi Wu > > wrote: >> >> You mean values of type String? > > I was speaking solely of c

Re: [swift-evolution] [Proposal] Normalize Unicode Identifiers

> On Sep 22, 2016, at 4:19 PM, Xiaodi Wu wrote: > > You mean values of type String? I was speaking solely of constant strings. > I would want those to be exactly what I say they are; NFC normalization is > available, if I recall, as part of Foundation, but by no means should my > String valu

Re: [swift-evolution] [Proposal] Normalize Unicode Identifiers

> On Sep 22, 2016, at 10:50 AM, Joe Groff via swift-evolution > wrote: > > >> On Jul 26, 2016, at 12:26 PM, Xiaodi Wu via swift-evolution >> wrote: >> >> +1. Even if it's too late for Swift 3, though, I'd argue that it's highly >> unlikely to be code-breaking in practice. Any existing code

Re: [swift-evolution] Should Swift apply "statement scope" for ARC

> On Sep 21, 2016, at 4:01 PM, John Holdsworth via swift-evolution > wrote: > > My contrived example was a bit flimsy. I’d better unpack the full story. The > real > code I had problems with was based around the following Java instance wrapper: > > open class JNIObject: JNIObjectProtocol { >

Re: [swift-evolution] [Proposal] Change some collection iterators to use custom types instead of IndexIterator

Submitted the following PR: https://github.com/apple/swift-evolution/pull/469 Michael > On Jul 22, 2016, at 2:35 PM, Michael Gottesman via swift-evolution > wrote: > > Hello everyone! > > Iterators are very important for performance since we use them for for loops. > B

[swift-evolution] [Proposal] Change some collection iterators to use custom types instead of IndexIterator

Hello everyone! Iterators are very important for performance since we use them for for loops. By default collections if they do not provide a custom iterator use IndexingIterator as an iterator. IndexingIterator, while only supporting forward movement, is based on indices which possess the abil

Re: [swift-evolution] [Proposal] Move public AutoreleasingUnsafeMutablePointer API from StdlibCore -> Objective C Overlay

> On Jul 22, 2016, at 11:42 AM, Dave Abrahams via swift-evolution > wrote: > > > on Fri Jul 22 2016, Ben Rimmington > wrote: > >>> On 21 Jul 2016, at 18:02, Michael Gottesman wrote: >>> >>> This is a proposal to move AutoreleasingUnsafeMutablePointer from >

[swift-evolution] [Proposal] Move public AutoreleasingUnsafeMutablePointer API from StdlibCore -> Objective C Overlay

Hello everyone. This is a proposal to move AutoreleasingUnsafeMutablePointer from StdlibCore to the Objective C overlay. The reason to do this is that ideally StdlibCore would not have any code specific to ObjC in it. This is a small step that we can take in this direction by moving the public

Re: [swift-evolution] Still Missing: Fixed Decimal Numerical Type.

+CC Steve > On Mar 30, 2016, at 6:09 AM, Ted F.A. van Gaalen via swift-evolution > wrote: > > There is still no fixed decimal numerical type available in Swift! > > It should be implemented *as soon as possible* > because the fixed decimal type is really needed > for applications working wi

Re: [swift-evolution] Notes from Swift core team 2016-03-15 design discussion

In the future, can you make each SE- into a link to the github page of the proposal? Michael > On Mar 16, 2016, at 5:27 PM, Alex Martini via swift-evolution > wrote: > > To help keep proposals moving forward, the Swift core team has set aside some > time specifically for design discussio

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

> On Mar 23, 2016, at 5:26 AM, Rainer Brockerhoff via swift-evolution > wrote: > > On 3/22/16 23:20, Michael Gottesman via swift-evolution wrote: >> >>> On Mar 18, 2016, at 3:42 PM, Rainer Brockerhoff via swift-evolution >>> wrote: >>> >

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

> On Mar 18, 2016, at 3:42 PM, Rainer Brockerhoff via swift-evolution > wrote: > > First draft towards a tentative pre-proposal: > https://gist.github.com/rbrockerhoff/6874a5698bb479886e83 > -- > > Pre-proposal: Safer Decimal Calculations > Proposal: TBD > Author(s): Rainer Brockerhoff > S