-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Fix LazyLock
poison panic message
#145307
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
Open
connortsui20
wants to merge
1
commit into
rust-lang:master
Choose a base branch
from
connortsui20:lazylock-poison-msg
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+69
−17
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -165,3 +165,32 @@ fn lazy_force_mut() { | |
p.clear(); | ||
LazyLock::force_mut(&mut lazy); | ||
} | ||
|
||
/// Verifies that when a `LazyLock` is poisoned, it panics with the correct error message ("LazyLock | ||
/// instance has previously been poisoned") instead of the underlying `Once` error message. | ||
#[test] | ||
#[cfg_attr(not(panic = "unwind"), ignore = "test requires unwinding support")] | ||
#[should_panic(expected = "LazyLock instance has previously been poisoned")] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The reason this test passes is because |
||
fn lazy_lock_poison_message() { | ||
let lazy: LazyLock<String> = LazyLock::new(|| panic!("initialization failed")); | ||
|
||
// First access will panic during initialization. | ||
let _ = panic::catch_unwind(|| { | ||
let _ = &*lazy; | ||
}); | ||
|
||
// Second access should panic with the poisoned message. | ||
let _ = &*lazy; | ||
} | ||
|
||
// Verifies that when the initialization closure panics with a custom message, that message is | ||
// preserved and not overridden by `LazyLock`. | ||
#[test] | ||
#[cfg_attr(not(panic = "unwind"), ignore = "test requires unwinding support")] | ||
#[should_panic(expected = "custom panic message from closure")] | ||
fn lazy_lock_preserves_closure_panic_message() { | ||
let lazy: LazyLock<String> = LazyLock::new(|| panic!("custom panic message from closure")); | ||
|
||
// This should panic with the original message from the closure. | ||
let _ = &*lazy; | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
catch_unwind
can't be used to override the panic message. By the timecatch_unwind
returns, the panic message has already been printed. In additioncatch_unwind
would cause an abort in case of a foreign exception.Maybe you can have an internal method like
call_once
except with a panic message as argument?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm that does make sense, but at the same time I think it's fine if the user gets 2 error messages?
I'm a bit worried about the footprint of updating the internal
call_once
method with a panic message as argument since that would require changing all of the underlying implementations as well. But if that is the only acceptable way then I'm happy to do it