On Feb 20, 2016, at 00:25 , Jean-Daniel Dupas <mail...@xenonium.com> wrote: > > Even if swift is planning to provide a Foundation framework, one of the > strong requirement is that it must be source compatible with the Apple > Foundation, as that is the one that will be used on Apple platforms. So if it > does not behave like NSString, it should be considered a bug.
Like with arrays, dictionaries and sets, it can have new APIs that are quite different and still bridge (in the Apple version of the Swift compiler) to Cocoa classes and APIs. There may end up being *two* flavors of string format specifiers. Or, perhaps the changes might percolate back to Cocoa. Lightweight generics are something along that line. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
