-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Tracking issue for std::sync::Once::is_completed #54890
Comments
The documentation needs to be made slightly more strict. For example:
Should be replaced with
The distinction is important, because at the exact moment this function returns To avoid people shotgunning their feet off, I would suggest to add some guidance on how this should be used. For example, doing something useful based on this function returning a |
CC @matklad for nagisa’s comment above. |
Fix tracking issue for Once::is_completed rust-lang#53027 was merged without a tracking issue. I just filed rust-lang#54890. CC @matklad
Fix tracking issue for Once::is_completed rust-lang#53027 was merged without a tracking issue. I just filed rust-lang#54890. CC @matklad
Fix tracking issue for Once::is_completed rust-lang#53027 was merged without a tracking issue. I just filed rust-lang#54890. CC @matklad
Fix tracking issue for Once::is_completed rust-lang#53027 was merged without a tracking issue. I just filed rust-lang#54890. CC @matklad
It's been 9 months since this was implemented. Can this be stabilized now? |
Is there anything preventing this method from being stabilized? It looks like there was some bikesheding in #53027 but it's now been just past a year since initial adoption. |
Note that I am personally no longer directly interested in having this method: in |
…albertodt Stabilize Once::is_completed Closes rust-lang#54890 This function has been around for some time. I haven't seen anyone raise any objections to it. I've personally found it useful myself. It would be nice to finally stabilize it and
Implemented in #53027
The text was updated successfully, but these errors were encountered: