-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can new arrays be allcoated on stack? #5
Comments
|
If an array object does not escape the current method, my guess is that we can allocate it on the stack -- the array object is just a single reference and destroying it doesn't remove the contained objects (if they escape, they will still be accessible from the reference that made them escape). For the second question, will the following work?
|
Should new array statements be tracked for their escape status or shall we just discard them as objects that escape?
The text was updated successfully, but these errors were encountered: