Right, I totally agree with you, but NSString compatibility would be problematic then:<br>let s: NSString <br>let s2 = s as String // this would have to be a failable cast<br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 19, 2015 at 9:57 AM Guillaume Lessard via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On 18 déc. 2015, at 14:47, Paul Cantrell via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> I was quite surprised to learn that it’s possible to create Swift strings that do not contain things other than valid Unicode characters. Is it feasible to guarantee that this cannot happen?<br>
<br>
That would be nice. I’m not sure that CFString or NSString guarantee correctness, though. If they don’t, then this could not be.<br>
<br>
Guillaume Lessard<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><div dir="ltr">-- <br></div>Javier Soto