Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Freeing garbage collected objects does not call drop #18

Closed
Marwes opened this issue Jan 2, 2016 · 2 comments
Closed

Freeing garbage collected objects does not call drop #18

Marwes opened this issue Jan 2, 2016 · 2 comments
Labels
bug
Milestone
0.1

Comments

@Marwes
Copy link
Member

Marwes commented Jan 2, 2016

No description provided.

@Marwes Marwes added the bug label Jan 2, 2016
@Marwes Marwes added this to the 0.1 milestone Jan 2, 2016
@Marwes
Copy link
Member Author

Marwes commented Jan 10, 2016

Due to the use of the Array type it is not possible to simply use ptr::read on the data in AllocPtr to drop the value. drop_in_place would allow the value to be dropped correctly but it is currently unstable.

rust-lang/rust#27908

@Marwes
Copy link
Member Author

Marwes commented Apr 15, 2016

Fixed in f9722cd 🎉

@Marwes Marwes closed this as completed Apr 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
1 participant
@Marwes