Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Tracking issue for --explain expansion #34827

Closed
alexcrichton opened this issue Jul 14, 2016 · 3 comments
Closed

Tracking issue for --explain expansion #34827

alexcrichton opened this issue Jul 14, 2016 · 3 comments
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@alexcrichton
Copy link
Member

Tracking issue for the --explain related portions of rust-lang/rfcs#1644

Current open questions are:

  • Let's look at an implementation! Does it end up being reasonable?
  • Is there a way to deprecate --explain <CODE> and instead use --explain to activate these errors?
  • Is it easy to template these longer explanations for authors?

cc @jonathandturner (feel free to fill out more)
@alexcrichton alexcrichton added B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jul 14, 2016
@alexcrichton alexcrichton mentioned this issue Jul 14, 2016
Merged
@GuillaumeGomez
Copy link
Member

Some error explanations are (I think) very easy to update to this new RFC. Some others (the longest or most "general" ones) are almost impossible as is. Some rework on these last ones is needed first (split them in smaller errors for example).

@brson brson added B-unstable Blocker: Implemented in the nightly compiler and unstable. and removed B-unstable Blocker: Implemented in the nightly compiler and unstable. labels Mar 1, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Jul 25, 2017
@Dylan-DPC-zz
Copy link

#61137

@GuillaumeGomez
Copy link
Member

Closing this one then.

@mbartlett21 mbartlett21 mentioned this issue Jun 11, 2021
Closed
100 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@alexcrichton @brson @GuillaumeGomez @Mark-Simulacrum @Dylan-DPC-zz