Yeah this is similar to what I’d imagined in the thread about ~Copyable x Codable—in both cases you have an out because you can throw/return nil, though in the case of LosslessStringConvertible it does feel slightly more against the spirit of the protocol. I don’t know that that rises to the level where it’s worth totally banning at the library level, though!
1 Like