-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
fix Miri assignment sanity check #70806
Conversation
// 2. Subtyping is used. While all normal lifetimes are erased, higher-ranked lifetime | ||
// bounds with their late-bound regions are still around and can lead to type differences. |
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.
"higher-ranked lifetime bounds" -> "higher-ranked types" (fn
types and dyn Trait
types are "higher-ranked" because they can "forall"-bind lifetimes - this is what the Binder
wrapper indicates)
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.
Done. I also replaced "regions" by "lifetimes".
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.
r=me with comment tweaked
@bors r=eddyb |
📌 Commit e52a451 has been approved by |
Rollup of 5 pull requests Successful merges: - rust-lang#70558 (Fix some aliasing issues in Vec) - rust-lang#70760 (docs: make the description of Result::map_or more clear) - rust-lang#70769 (Miri: remove an outdated FIXME) - rust-lang#70776 (clarify comment in RawVec::into_box) - rust-lang#70806 (fix Miri assignment sanity check) Failed merges: r? @ghost
Thanks @eddyb for pointing me to the right APIs!
r? @eddyb
Fixes #70804