fix implied_bounds_entailment lint
#2
Merged
Conversation
This file contains 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
|
Thank you for fixing this here, and throughout the ecosystem! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey 👋 this crate unintentionally relied on a soundness bug in the Rust compiler, see rust-lang/rust#105572 for more info. This lint will be a hard error in a future release and is fixed by this PR.
The issue was that inside of
deref, we assume thatSelf::Targethas to life to'staticeven though that's never proven by the caller ofderefbecausederefreturns&'static Self::Target. Users ofDerefforStatic<T>always only used the signature of the trait method, so the stronger bound on the impl did not impact them.