Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

on Tue Jul 05 2016, Dmitri Gribenko wrote: > On Tue, Jul 5, 2016 at 9:24 PM, Chris Lattner wrote: >> On Jul 5, 2016, at 6:57 PM, Dmitri Gribenko via swift-evolution >> wrote: >>> >>> Hi swift-evolution, >>> >>> Dave,

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

> On 7 Jul 2016, at 03:15, Karl wrote: > > >> On 7 Jul 2016, at 02:06, Dmitri Gribenko > > wrote: >> >> On Wed, Jul 6, 2016 at 4:21 AM, Karl > > wrote: >>> I had

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

On Wed, Jul 6, 2016 at 6:15 PM, Karl wrote: > > On 7 Jul 2016, at 02:06, Dmitri Gribenko wrote: > > On Wed, Jul 6, 2016 at 4:21 AM, Karl wrote: > > I had a PR open for this which added a Collection specialisation, but you > said this

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

> On 7 Jul 2016, at 02:06, Dmitri Gribenko wrote: > > On Wed, Jul 6, 2016 at 4:21 AM, Karl wrote: >> I had a PR open for this which added a Collection specialisation, but you >> said this could be handled in a more general way which allows for more >>

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

On Wed, Jul 6, 2016 at 4:21 AM, Karl wrote: > I had a PR open for this which added a Collection specialisation, but you > said this could be handled in a more general way which allows for more > optimised mutations. I’m curious how this would work; how does >

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

on Wed Jul 06 2016, Jacob Bandes-Storch wrote: > On Tue, Jul 5, 2016 at 10:50 PM, Dmitri Gribenko via swift-evolution < > swift-evolution@swift.org> wrote: > >> >> > Remove unsafeAddressOf. We are not aware of any real usecases for it. If >> there are any, it should be renamed to

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

on Wed Jul 06 2016, Karl wrote: > I’m quite interested in this point: > >> Figure out whether RangeReplaceableCollection.replaceRange should accept a >> Sequence as its argument, and if so implement it. > > At the moment `replaceSubrange` takes a sequence, No, actually at the moment it takes

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

On Wed, Jul 6, 2016 at 11:30 AM, Harlan Haskins wrote: > I’ve also seen unsafeAddressOf(_:) used when interfacing with C function > pointers when the lifetime of an object is guaranteed. Many C APIs vend an > API like: > > void perform_action(void (*callback)(void

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

I’ve also seen unsafeAddressOf(_:) used when interfacing with C function pointers when the lifetime of an object is guaranteed. Many C APIs vend an API like: void perform_action(void (*callback)(void *data), void *initial_data); For which it is expected to use unsafeAddressOf on a class

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

On Tue, Jul 5, 2016 at 10:50 PM, Dmitri Gribenko via swift-evolution < swift-evolution@swift.org> wrote: > > > Remove unsafeAddressOf. We are not aware of any real usecases for it. If > there are any, it should be renamed to unsafeAddress(of:) to follow the > guidelines. > Obvious, unless someone

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

> On Jul 5, 2016, at 11:50 PM, Dmitri Gribenko via swift-evolution > wrote: > > On Tue, Jul 5, 2016 at 9:24 PM, Chris Lattner > wrote: >> On Jul 5, 2016, at 6:57 PM, Dmitri Gribenko via swift-evolution >>

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

I’m quite interested in this point: > Figure out whether RangeReplaceableCollection.replaceRange should accept a > Sequence as its argument, and if so implement it. At the moment `replaceSubrange` takes a sequence, and lots of methods on RangeReplaceableCollection use that to perform their

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

On Tue, Jul 5, 2016 at 9:24 PM, Chris Lattner wrote: > On Jul 5, 2016, at 6:57 PM, Dmitri Gribenko via swift-evolution > wrote: >> >> Hi swift-evolution, >> >> Dave, Max and I have compiled a list of open issues in the standard >> library for which

Re: [swift-evolution] Open Issues Affecting Standard Library API Stability

On Jul 5, 2016, at 6:57 PM, Dmitri Gribenko via swift-evolution wrote: > > Hi swift-evolution, > > Dave, Max and I have compiled a list of open issues in the standard > library for which the resolutions could result non-additive API > changes. Having a resolution

[swift-evolution] Open Issues Affecting Standard Library API Stability

Hi swift-evolution, Dave, Max and I have compiled a list of open issues in the standard library for which the resolutions could result non-additive API changes. Having a resolution (and an implementation of the resolution!) for these issues is blocking API stability.