We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
If I understand the reasoning behind marking mem::forget safe, then I think the same should apply to into_raw.
mem::forget
into_raw
Currently, it says:
Function is unsafe, because result of this function is no longer automatically managed that may lead to memory or other resource leak.
The text was updated successfully, but these errors were encountered:
Agreed. It's safe. Basically a mem::forget that returns an integer.
Sorry, something went wrong.
Mark boxed::into_raw as safe
boxed::into_raw
04ab4a3
By the same logic that `mem::forget` is safe, `boxed::into_raw` is actually a safe function. Fixes rust-lang#25755.
Auto merge of #25767 - mystor:patch-1, r=Gankro
20047f1
By the same logic that `mem::forget` is safe, `boxed::into_raw` is actually a safe function. Fixes #25755.
7cb9914
Successfully merging a pull request may close this issue.
If I understand the reasoning behind marking
mem::forget
safe, then I think the same should apply tointo_raw
.Currently, it says:
The text was updated successfully, but these errors were encountered: