.withUnsafeMutableBufferPointer doesn't work either, for reference.
ratkins
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Has anyone indeed started this discussion? I can't find one, and I would very much like to understand the justification behind this limitation.
Beta 1 you mean, released October 27?
Oh holy crap you're right—I have also had this "Xcode eats all the memory" bug, but it seems the fix detailed in that link has given me my processors back. Thanks!