I hope someone making C++ compilers picks up on this. Elm has *amazing* compiler error messages. Just one example: http://elm-lang.org/blog/compilers-as-assistants …
-
-
Replying to @sehurlburt
We've been trying this for Rust but aren't as good yet. I prefer it to gcc/clang's error messages though. Elm is amazing!
1 reply 1 retweet 11 likes -
Replying to @ManishEarth
Is there a good post you recommend about Rust's compiler error messages?
2 replies 0 retweets 2 likes -
Replying to @sehurlburt
We have https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-come.html … talking about improvements to the borrow error messages. Not all of those have happened.
1 reply 3 retweets 7 likes -
Replying to @ManishEarth @sehurlburt
But ours aren't amazing like Elms so we don't really talk about them in blog posts :)
1 reply 0 retweets 3 likes -
Replying to @ManishEarth @sehurlburt
Personally the "suggestions" are my favorite!pic.twitter.com/KASqZ95vJE
4 replies 2 retweets 23 likes -
Replying to @ManishEarth @sehurlburt
I used to put a lot of time into these and now I'm too busy to do so, but others are working on improving them!
1 reply 0 retweets 1 like -
Replying to @ManishEarth @sehurlburt
I also love that you can do `rustc --explain E0373` there and get something like https://doc.rust-lang.org/nightly/error-index.html#E0373 … in the terminal output.
2 replies 2 retweets 9 likes -
Replying to @ManishEarth @sehurlburt
Now we just need `rustc --explain WhyIsThisTypeLongerThanMyTerminalScrollbackBuffer`
2 replies 0 retweets 1 like -
Replying to @sgrif @sehurlburt
$ rustc --explain WhyIsThisTypeLongerThanMyTerminalScrollbackBuffer Because
@sgrif wrote That One Crate.
2 replies 1 retweet 3 likes
Replying to @ManishEarth @sehurlburt
Futures is just as bad. :P
12:49 PM - 14 May 2017
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.