> I agree. The major motivation from my side isn’t the code size reduction, it > is that we’ll have a better and brighter future with more clarity and less > weird cruft left over - like the “DictionaryLiteral” type that sparked this > whole thread. Have you looked at it? It’s crazy. :-)
+1 One of the things that I like about Swift (vis-à-vis C++, Java, JavaScript etc) is that the Core team is not afraid to fix ‘historical mistakes’. I think, Chris’ idea of a separate unstable/deprecated dylib provides an excellent platform for this practice to continue after ABI stability. -g. _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
