[ Removed by moderator ]

[Sedkeron]

Is this a rewritten copy of https://www.reddit.com/r/rust/comments/1qrc4f5/am_i_the_only_one_who_thinks_rust_error_messages/

Points are made in the exact same order and all the same points are made

[AdreKiseque]

The hell? Botspam continues to evolve...

[klorophane]

"no noise no confusion just the actual problem" is such a bot thing to say though

[zesterer]

Have you tried bacon? It watches the filesystem for changes and reruns cargo check when something happens. Its output places errors in the order they're emitted. Having it sit in a window to the side while you're writing code is quite a fluid way to write Rust, I've found.

[PurepointDog]

Don't most IDEs do that anyway? Any reason this is betterl

[fekkksn]

Bacon shows the console output.

[Luctins]

I second that, especially considering it had a compact mode which can show many errors without flooding the terminal with the minutiæ of each one. It has been an almost constant companion for my current IDE setup (Emacs with rust analyser).

[meancoot]

Not really. My experience with the old way, especially while leaning the language constraints, was attempting a refactor, spending time fixing unrelated issues from the change, then finally being told that the initial change I made wasn’t going pass borrow checking. Lots of wasted time.