You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating clusters like NSString, NSNumber NSDictionary etc we have to pollute the subclasses with ivars and we don't have uniqueness like [NSNumber numberWithBool:]'s return value being identical or NSNull being identical to all creations.
This leads to either poor performance and memory thrashing, or it will lead to divergent interfaces that make the swift-corelibs-foundation behave differently than the darwin objc version.
Proposals have been floated around for this and it seems amenable; however it would be nice to pick those up in as official proposals to un-block the development of Foundation with swift.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: c72472827065bb4d1b05fda9a937428f
blocks:
Issue Description:
When creating clusters like NSString, NSNumber NSDictionary etc we have to pollute the subclasses with ivars and we don't have uniqueness like [NSNumber numberWithBool:]'s return value being identical or NSNull being identical to all creations.
This leads to either poor performance and memory thrashing, or it will lead to divergent interfaces that make the swift-corelibs-foundation behave differently than the darwin objc version.
Proposals have been floated around for this and it seems amenable; however it would be nice to pick those up in as official proposals to un-block the development of Foundation with swift.
The text was updated successfully, but these errors were encountered: