-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Let user see the full type of type-length limit error #76843
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
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.
Writing a file as part of diagnostics is novel AFAICT, but seems like the right thing to do in this case. One question, will cargo clean
remove this?
ee35975
to
be65c12
Compare
The path is chosen by an existing function for temp files (it's very handy that rustc already has that), and |
@bors delegate+ rollup r=me with or without suggestion and with tests passing. |
✌️ @kornelski can now approve this pull request |
@bors r+ |
📌 Commit 677c6fcfe47471614abc2f6aed0e9e16cbda0790 has been approved by |
☔ The latest upstream changes (presumably #72412) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
677c6fc
to
c5968e8
Compare
@bors r+ |
📌 Commit c5968e8 has been approved by |
@bors r- r=ecstatic-morse @kornelski please use the name of the reviewer when delegated to. |
📌 Commit c5968e8 has been approved by |
…c-morse Let user see the full type of type-length limit error Seeing the full type of the error is sometimes essential to diagnosing the problem, but the type itself is too long to be displayed in the terminal in a useful fashion. This change solves this dilemma by writing the full offending type name to a file, and displays this filename as a note. > note: the full type name been written to '$TEST_BUILD_DIR/issues/issue-22638/issue-22638.long-type.txt' Closes rust-lang#76777
Failed in #76957 (comment) |
c5968e8
to
34d3c7d
Compare
build path normalization doesn't cover nll tests. I've added explicit normalization for them. |
@bors r=ecstatic-morse rollup=iffy |
📌 Commit 34d3c7d has been approved by |
☀️ Test successful - checks-actions, checks-azure |
Seeing the full type of the error is sometimes essential to diagnosing the problem, but the type itself is too long to be displayed in the terminal in a useful fashion. This change solves this dilemma by writing the full offending type name to a file, and displays this filename as a note.
Closes #76777