[swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

> Hello, Swift community! > > The review of "SE-163: String Revision: Collection Conformance, C Interop, > Transcoding" begins now and runs through next Tuesday, April 11th. The > proposal is available here: > https://github.com/apple/swift-evolution/blob/master/proposals/0163-string-revision-1.

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

+1 with this clarification / revision > On Apr 6, 2017, at 5:34 PM, Ben Cohen via swift-evolution > wrote: > > >> On Apr 5, 2017, at 10:32 PM, Félix Cloutier > > wrote: >> >> During the proposal phase, we asked how this would handle fixed-length >> strings with an o

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

It probably depends on the positioning of the initializer. I strongly associate the collection initializer to the special case of UnsafeBufferPointer, and the result strings will probably be passed back to C at some point, where an embedded NUL terminates the string (inconsistently with what Swi

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

> On Apr 5, 2017, at 10:32 PM, Félix Cloutier wrote: > > During the proposal phase, we asked how this would handle fixed-length > strings with an optional NUL terminator. For instance, in a C `struct Foo { > char name[8]; };`, `name` stops at the first \0, or at the eighth byte, > whichever c

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

> On Apr 5, 2017, at 12:39 PM, John McCall via swift-evolution > wrote: > > Hello, Swift community! > > The review of "SE-163: String Revision: Collection Conformance, C Interop, > Transcoding" begins now and runs through next Tuesday, April 11th. The > proposal is available here: > >

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

+1. This is well thought out and an important evolution of string. > On Apr 5, 2017, at 11:39 AM, John McCall via swift-evolution > wrote: > > Hello, Swift community! > > The review of "SE-163: String Revision: Collection Conformance, C Interop, > Transcoding" begins now and runs through next

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

> On 6 Apr 2017, at 4:39 am, John McCall via swift-evolution > wrote: > > Hello, Swift community! > > The review of "SE-163: String Revision: Collection Conformance, C Interop, > Transcoding" begins now and runs through next Tuesday, April 11th. The > proposal is available here: > > h

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

During the proposal phase, we asked how this would handle fixed-length strings with an optional NUL terminator. For instance, in a C `struct Foo { char name[8]; };`, `name` stops at the first \0, or at the eighth byte, whichever comes first. IIRC, Ben said that it would be handled, but I'd like

Re: [swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

On Wed, Apr 5, 2017 at 1:39 PM, John McCall via swift-evolution < swift-evolution@swift.org> wrote: > Hello, Swift community! > > The review of "SE-163: String Revision: Collection Conformance, C Interop, > Transcoding" begins now and runs through next Tuesday, April 11th. The > proposal is availa

[swift-evolution] SE-163: String Revision: Collection Conformance, C Interop, Transcoding

Hello, Swift community! The review of "SE-163: String Revision: Collection Conformance, C Interop, Transcoding" begins now and runs through next Tuesday, April 11th. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/proposals/0163-string-revision-1.md