Suggest copying trait associated type bounds on lifetime error#92683
Suggest copying trait associated type bounds on lifetime error#92683bors merged 1 commit intorust-lang:masterfrom
Conversation
There was a problem hiding this comment.
This and the one below are drive-by changes. These shouldn't ever be displayed anyways. But wanted to stop using from_obligation_cause (was potentially going a different direction for this PR).
There was a problem hiding this comment.
This bound was required because of a bug that has since been fixed. FIXME still stands for the two remaining though.
|
r=me but I'll let @estebank do a review if he wants to |
|
☔ The latest upstream changes (presumably #92927) made this pull request unmergeable. Please resolve the merge conflicts. |
9bac686 to
814a62d
Compare
|
☔ The latest upstream changes (presumably #92007) made this pull request unmergeable. Please resolve the merge conflicts. |
|
r=me after fixing rebase |
814a62d to
3d19c8d
Compare
|
@bors r=estebank |
|
📌 Commit 3d19c8d has been approved by |
Suggest copying trait associated type bounds on lifetime error Closes rust-lang#92033 Kind of the most simple suggestion to make - we don't try to be fancy. Turns out, it's still pretty useful (the couple existing tests that trigger this error end up fixed - for this error - upon applying the fix). r? `@estebank` cc `@nikomatsakis`
…askrgr Rollup of 6 pull requests Successful merges: - rust-lang#92683 (Suggest copying trait associated type bounds on lifetime error) - rust-lang#92933 (Deny mixing bin crate type with lib crate types) - rust-lang#92959 (Add more info and suggestions to use of #[test] on invalid items) - rust-lang#93024 (Do not ICE when inlining a function with un-satisfiable bounds) - rust-lang#93613 (Move `{core,std}::stream::Stream` to `{core,std}::async_iter::AsyncIterator`) - rust-lang#93634 (compiler: clippy::complexity fixes) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Closes #92033
Kind of the most simple suggestion to make - we don't try to be fancy. Turns out, it's still pretty useful (the couple existing tests that trigger this error end up fixed - for this error - upon applying the fix).
r? @estebank
cc @nikomatsakis