> To answer my own question, relooking at the proposal, RawRepresentable 
> wouldn’t be suitable for Bool, Character, UnicodeScalar, Integer, etc.
> 
>> On 5 Jun 2016, at 7:20 PM, Patrick Smith <[email protected]> wrote:
>> 
>> (This raises a point — what’s the difference between the proposed 
>> LosslessStringConvertible and RawRepresentable where RawValue = String? They 
>> both have a failable init. Is it due to current limitations with typealiases 
>> that makes this hard?)

I would add that RawRepresentable does not promise the representation is 
human-readable.

-- 
Brent Royal-Gordon
Architechies

_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to