Uh oh!
There was an error while loading. Please reload this page.
Add short error message-format - #44636
Conversation
rust-highfive
commented
Sep 16, 2017
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
eddyb
commented
Sep 16, 2017
r? @nrc |
1b3f2be to
9ad8252Comparenrc
commented
Sep 19, 2017
Rather than adding a new emitter, could you have the human-readable emitter take an argument for detail level - either short or verbose? It seems that we'd save a lot of code dup (and a macro) that way. Could you put this behind a feature gate? |
GuillaumeGomez
commented
Sep 19, 2017
Yes and yes. I was just thinking that we'd want to fully split both of the features but if not... |
8468a5f to
a58becdCompareGuillaumeGomez
commented
Sep 19, 2017
Ok, now just remain to put it behind a feature flag. |
kennytm
commented
Sep 20, 2017
Is it possible to make each error only occupy one line, similar to Mock up: |
eddyb
commented
Sep 20, 2017
@kenny |
@eddyb That sample is referring to the UI test in this PR https://github.com/GuillaumeGomez/rust/blob/a58becd60d7d7a965ed246cf8e290e2bd94043b9/src/test/ui/short-error-format.stderr: Improving E0308 could happen independent of this PR. |
Oh yeah, in that case, I agree, the example output in #44636 (comment) is a subset of the lines I have from my |
GuillaumeGomez
commented
Sep 20, 2017
So which output do you want? So I can do it once and for all. :) |
d598684 to
30128d6Compareestebank
commented
Sep 22, 2017
I feel if the idea is to use as little vertical space the output should be closer to: Beyond that, I wonder wether it'd be worth it to try to keep in the diagnostic machinery space for custom single line error messages that would work better for short output (and for text editors). May be I'll just go ahead and introduce it for while and see how much of a pain it becomes. If it is too much, we can rip it out. I do feel strongly against improving things for text editors in detriment of cli output. |
30128d6 to
bec51daCompareGuillaumeGomez
commented
Sep 24, 2017
New output available! |
bec51da to
a4b28f2CompareGuillaumeGomez
commented
Oct 20, 2017
The branch has been created on |
GuillaumeGomez
commented
Oct 21, 2017
We now have the following error: Anyone has an idea? |
topecongiro
commented
Oct 21, 2017
@GuillaumeGomez Could you please use |
fff79bd to
3f68f78CompareGuillaumeGomez
commented
Oct 21, 2017
Ok, let's hope it'll be the good one this time. :) |
GuillaumeGomez
commented
Oct 21, 2017
New error and it doesn't get any better: Anyone has an idea? |
3f68f78 to
b46c014CompareGuillaumeGomez
commented
Oct 24, 2017
Fixed. |
michaelwoerister
commented
Oct 25, 2017
@bors r+ |
bors
commented
Oct 25, 2017
📌 Commit b46c014 has been approved by |
bors
commented
Oct 25, 2017
…ister Add short error message-format Fixes#42653.
bors
commented
Oct 25, 2017
☀️ Test successful - status-appveyor, status-travis |
alexcrichton
commented
Nov 14, 2017
@nrc@GuillaumeGomez this landed without a feature flag, was that intentional? I assume not given #44636 (comment)? |
nrc
commented
Nov 15, 2017
I suppose this should be behind Thanks for noticing @alexcrichton ! |
GuillaumeGomez
commented
Nov 15, 2017
Hum indeed, it should had have a feature flag. I'll add it as soon as possible. |
vitiral
commented
Feb 1, 2018
❤️ Thanks for fixing the bug I reported, looking forward to using this when it becomes available! |
vitiral
commented
Feb 1, 2018
On this comment my preference would be something like: It's all in one line but that's probably okay. That's just, like, my opinion though man. |
…r-format, r=oli-obk Stabilize short error format r? @oli-obk Added in rust-lang#44636
Fixes#42653.