I’ve been thinking that it would be good to improve the hints/tips that the compiler offers to target the 2018 edition features directly. As a simple example, if one writes:
foo is a global module, then the compiler should suggest
use crate::foo::bar as a replacement.
On a more complex note, there have definitely been times when match default bindings can surprise people – e.g., you end up with a reference but don’t expect it. I have some thoughts about how to address that but it would be really helpful to have examples of code that didn’t compile where you had to scratch your head a bit. I assume there may be other features leading to surprises of this kind.
So I am starting this thread to request examples of code snippets where you think an improved error would’ve helped – ideally, with some notes on what you confused you specifically (if it is not obvious) or a suggestion you think would’ve helped.