diagnostics: improve message when empty#154232
diagnostics: improve message when empty#154232Jengamon wants to merge 1 commit intorust-lang:mainfrom
Conversation
This comment has been minimized.
This comment has been minimized.
|
Hi! Thanks for your contribution! Take your time, and mark this as ready for review whenever you're set. Feel free to ask any questions along the way -- happy to help! |
This comment has been minimized.
This comment has been minimized.
Thanks @Kivooeo! I have 2 right off the bat:
|
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
Sorry for the late reply -- I spent some time digging into this issue today and tried a few different approaches, but I should note that it turned out to be a bit more complex than it seemed at first glance. As for the expected output in the tests, yes, you can definitely change it if needed. The main thing is to make sure the error messages don't become worse or less informative across different scenarios - that's what we need to watch out for. For example, in the |
|
My instinct is that if we can get the difference between I run on a looooot this is the short version and no worries Im just really free rn. |
This adds a more accurate suggestion around the program
by suggesting a fix to
TODO
Option(T)is being suggested by the compiler in the second error (E0107)Option<T>insteadFixes #154220