Change how closure and generator types are printed to avoid clash with slice types #675
Closed
1 of 3 tasks
Labels
major-change
A proposal to make a major change to rustc
major-change-accepted
A major change proposal that was accepted
T-compiler
Add this label so rfcbot knows to poll the compiler team
Proposal
When the compiler has to print the type of a closure or generator, it currently looks like this:
[closure@$DIR/issue-20862.rs:2:5]
. The choice of using brackets here is unfortunate, since it means a reference-to-closure&[closure@$DIR/issue-20862.rs:2:5]
looks like a slice type! I was quite confused by this recently.Hence I propose we change this to use curly braces instead, which don't already have a meaning as types:
&{closure@$DIR/issue-20862.rs:2:5}
.This has been implemented in rust-lang/rust#115696.
Mentors or Reviewers
@oli-obk
Process
The main points of the Major Change Process are as follows:
@rustbot second
.-C flag
, then full team check-off is required.@rfcbot fcp merge
on either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: