Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-05 Thread Andrew Trick via swift-evolution
“as” is for types :) Let’s say initialize(to:) is good and once we’ve bikeshedded all the other names we’ll see if there’s any potential for confusion… Andy > On Jul 5, 2016, at 9:20 AM, Dave Abrahams wrote: > > The use "as"? > > Sent from my moss-covered three-handled

Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-05 Thread Dave Abrahams via swift-evolution
The use "as"? Sent from my moss-covered three-handled family gradunza > On Jul 5, 2016, at 6:48 AM, Andrew Trick wrote: > > >>> On Jul 4, 2016, at 6:19 PM, Dave Abrahams via swift-evolution >>> wrote: >>> >>> So Swift 3 users have already

Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-05 Thread Anton Zhilin via swift-evolution
func initialize(_: T.Type, to: T, count: Int = 1) -> UnsafeMutablePointer I wonder why the first parameter is needed. If one is passing literals, it's always more Swift'y to use 'as'. 2016-07-05 6:00 GMT+03:00 L. Mihalkovic via swift-evolution < swift-evolution@swift.org>: > > > Regards >

Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-04 Thread L. Mihalkovic via swift-evolution
Regards (From mobile) > On Jul 3, 2016, at 10:18 AM, Andrew Trick via swift-evolution > wrote: > > >> On Jul 2, 2016, at 8:10 PM, Brent Royal-Gordon via swift-evolution >> wrote: >> >> I have a pile of naming quibbles; rather than

Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-04 Thread Dave Abrahams via swift-evolution
on Sun Jul 03 2016, Andrew Trick wrote: >> On Jul 2, 2016, at 8:10 PM, Brent Royal-Gordon via swift-evolution >> wrote: >> >> I have a pile of naming quibbles; rather than describe them all in >> prose (which turned into a mess), I've

Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-03 Thread Xiaodi Wu via swift-evolution
Being consistent with existing convention is good; I also agree it happens to make perfect sense anyway. On Sun, Jul 3, 2016 at 03:18 Andrew Trick via swift-evolution < swift-evolution@swift.org> wrote: > > On Jul 2, 2016, at 8:10 PM, Brent Royal-Gordon via swift-evolution < >

Re: [swift-evolution] [Review] SE-0107: UnsafeRawPointer API (initialize:with:)

2016-07-03 Thread Andrew Trick via swift-evolution
> On Jul 2, 2016, at 8:10 PM, Brent Royal-Gordon via swift-evolution > wrote: > > I have a pile of naming quibbles; rather than describe them all in prose > (which turned into a mess), I've annotated parts of the "Full > UnsafeRawPointer API" section in a gist: >