[swift-evolution] [swift-evolution-announce] [Review] SE-0027 Expose code unit initializers on String
gili.patrick.r at gili-labs.com
Sat Feb 13 16:33:37 CST 2016
Okay. However, does this change the implied semantics?
> On Feb 13, 2016, at 5:26 PM, Brent Royal-Gordon <brent at architechies.com> wrote:
>> The introduction starts out by making the claim, "Going back and forth from Strings to their byte representations is an important part of solving many problems, including object serialization, binary and text file formats, wire/network interfaces, and cryptography." Essentially, these problems deal with an array of raw bytes, and I have to wonder why an application would push them into a String?
> I read this section as trying to say "object serialization, binary and text file formats, wire/network interfaces, and cryptography all require you to construct strings from decoded bytes, which is what this proposal is trying to improve". I don't think it's trying to say that we should have better support for treating strings as bags of arbitrary bytes, and in fact I don't think this proposal does that.
> Brent Royal-Gordon
More information about the swift-evolution