>> >> The whole discussion started because ArrayLiteralConvertible meant "can be >> initialized from Array literal", and not "can be converted to array >> literal", which is what nearly everyone this was presented to in an informal >> study thought it meant. >> > > That was not the genesis of this proposal in my mind. I was frustrated with > the different semantics for Convertible between CustomStringConvertible and > *LiteralConvertible.
That's where *I* jumped on board. Sorry, I should have made it clearer. > However, I do agree that there is some potential for ambiguity inherent in > the term Convertible which is probably how the current conflicting uses arose > in the first place. > > Whatever we decide to do, I hope we can at least remove the current conflict > and have consistent meanings in the standard library! No matter how the core team rules, I hope there's an improvement over the status quo. -- E
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
