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.

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

Mark OnceState::poison as pub #133240

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GrigorenkoPV
Copy link
Contributor

Rebase of #130330 with #130330 (comment) fixed

Tracking issue: #130327

@rustbot
Copy link
Collaborator

rustbot commented Nov 20, 2024

r? @tgross35

rustbot has assigned @tgross35.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 20, 2024
Comment on lines 207 to 220
///
/// Poison a [`Once`] by explicitly calling [`OnceState::poison`]:
///
/// ```
/// #![feature(once_poison_pub)]
///
/// use std::sync::Once;
///
/// static INIT: Once = Once::new();
///
/// // poison the once without panicking
/// INIT.call_once_force(|p| p.poison());
/// INIT.call_once_force(|p| assert!(p.is_poisoned()));
/// ```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These docs look a bit off, maybe from the rebase? This example would be better in the docs for poison, and the heading "Poison a [Once] by panicking in a call_once closure:" is added twice (once here, once above the existing example).

@tgross35
Copy link
Contributor

It looks like this hasn't had an ACP or libs-api approval yet

r? libs-api

@rustbot rustbot added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label Nov 20, 2024
@rustbot rustbot assigned joshtriplett and unassigned tgross35 Nov 20, 2024
@rust-log-analyzer

This comment has been minimized.

@tgross35
Copy link
Contributor

tgross35 commented Dec 19, 2024

@GrigorenkoPV it is probably easiest to move this forward if you file an ACP at https://github.com/rust-lang/libs-team/issues, could you do that?

@GrigorenkoPV
Copy link
Contributor Author

@GrigorenkoPV it is probably easiest to move this forward if you file an ACP at https://github.com/rust-lang/libs-team/issues, could you do that?

Done:

@rustbot label +S-waiting-on-ACP

@rustbot rustbot added the S-waiting-on-ACP Status: PR has an ACP and is waiting for the ACP to complete. label Dec 19, 2024
@bors
Copy link
Contributor

bors commented Jan 3, 2025

☔ The latest upstream changes (presumably #134692) made this pull request unmergeable. Please resolve the merge conflicts.

@GrigorenkoPV GrigorenkoPV force-pushed the once_state_poison_pub branch from 967fb97 to 4f6e873 Compare January 3, 2025 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-ACP Status: PR has an ACP and is waiting for the ACP to complete. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants