Add regression test for trait on next solver - #161170
Open
lsunsi wants to merge 1 commit into
Open
Conversation
rustbot
added
S-waiting-on-review
Collaborator
|
r? @chenyukang rustbot has assigned @chenyukang. Use Why was this reviewer chosen?The reviewer was selected based on:
|
lsunsi
commented
Aug 16, 2026
|
|
||
| pub trait Bar: Sized { | ||
| async fn new() -> impl Fn<()> { | ||
| //~^ ERROR: the precise format of `Fn`-family traits' type parameters is subject to change |
Contributor
Author
There was a problem hiding this comment.
The four identical errors seem a little verbose and I couldn't reproduce them in a new project (where it only showed one of them). Should this be a diagnostics issue?
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Closes #151306.
The new test crashes on commit 37d85e5 (nightly-2026-04-29).
The new test fails (but not crashes) due to different stderr since c935696 (nightly-2026-04-30).
Ofc the test passes on current version.
Also, I took the liberty of adding a few bits of code to the minimal reproduction shared in the original issue just to make the stderr less verbose and we can focus on the issue that really matters. So I added main, removed the lifetimes, etc.
It's more code, but I'd argue is easier to reason for a test, although I'd obviously revert back to the minimal example if the reviewer thinks it's best.