Re: [swift-evolution] [Pitch] Improve String Literals

On Sat, May 13, 2017 at 1:42 AM, David Hart wrote: > > On 12 May 2017, at 23:14, Xiaodi Wu wrote: > > I feel like a broken record: Of the three proposed components of the > proposed solution, two were amply considered by the community and the core > team

Re: [swift-evolution] [Review] SE-0176: Enforce Exclusive Access to Memory

https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md What is your evaluation of the proposal? +1 It seems to be a carefully considered

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0178: Add unicodeScalars property to Character

It would be nice if character was made to be like a string of exactly length 1 (cannot be empty) and implemented the new string protocol like the new string slice does. This way string, string slice, and character could be used interchangeably when programming to the protocol. -- Howard. On 13

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0176: Enforce Exclusive Access to Memory

+1, the benefits outweigh the extra restrictions. Particularly since it is easy to add an escaping annotation if you think the compiler is wrong. However this will require careful documentation and good error messages so that people know why it fails to type check and how to overcome that. --

Re: [swift-evolution] [Pitch] Improve String Literals

> On 12 May 2017, at 23:14, Xiaodi Wu wrote: > > I feel like a broken record: Of the three proposed components of the proposed > solution, two were amply considered by the community and the core team in > SE-0168. The decision has already been made _not_ to implement