> On Apr 5, 2017, at 12:39 PM, John McCall via swift-evolution
> <[email protected]> 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:
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0163-string-revision-1.md
>
> <https://github.com/apple/swift-evolution/blob/master/proposals/0163-string-revision-1.md>
> • What is your evaluation of the proposal?
+1, looks great
> • Is the problem being addressed significant enough to warrant a change
> to Swift?
> • Does this proposal fit well with the feel and direction of Swift?
yes to both
> • If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
I’ve yet to use a language with Swift’s unicode capabilities, but I might
compare to Ruby 1.9+ strings, which support all encodings with one type. In
comparison, I greatly prefer the “forcing” of the unicode and extended grapheme
clusters mental model, rather than presenting a developer with sets of both
array-of-characters and array-of-bytes semantics at once
> • How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
Quick reading of proposal as well as reading of the String manifesto before.
-DW
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
