Thanks for the clarification. I wasn’t sure if alloc and new needed to be exposed to support some particular functionality - I’m glad to hear that this isn’t necessary.
Thanks for all of the great work that everyone has been doing on Swift. Your team is really amazing. Sincerely, Michael Patrick Ellard > On Feb 17, 2015, at 9:32 AM, Chris Lattner <[email protected]> wrote: > > On Feb 13, 2015, at 12:17 PM, Mike Ellard > <[email protected] > <mailto:[email protected]>> wrote: >> I was exploring the NSObject documentation for Swift and I was surprised to >> see that alloc is callable in Swift. >> What I would expect: >> >> A) Swift would not expose alloc or `new` at all. There shouldn’t be a way >> to create objects without going through an initializer. > > Hi Mike, > > You’re right, new and alloc shouldn’t be exposed to a Swift programmer. They > are effectively an implementation detail (which isn't memory safe to expose > as you point out). Thanks for filing the radar, we’ll take care of it when > we can. > > -Chris
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
