> On 31 Dec 2015, at 2:10 PM, Philippe Hausler <phaus...@apple.com> wrote: > > I think those are all pretty reasonable. The pipeline for changes is > bi-directional; however it will have to get reviewed by the component owner > and undergo our process to change API behavior internally. I am fairly > certain that this is an edge case that hasn’t even been thought of and I > would think that the rest of the Foundation team will be very apt to nail > this down so we don’t have to worry about backwards compatibility problems > that using the mangled name might incur in the future.
Right, NB the behaviour is really in libobjc’s objc_lookUpClass/class_getName. — Luke _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
