[proneb1rd]

I used to code with sublime and compile from time to time to check with compiler. Sometimes I’d go for an hour without running cargo and somehow it worked fine.

I have been doing rust since about 2016, in and out, and never questioned the approach but the tooling had improved dramatically in recent years.

I have switched to VSCode with rust-analyser and a few other extensions, which not only display errors but also types of variables which seems like a killer feature for me because it makes it so much easier.

I wonder what’s the motivation behind bacon given that it looks a bit outdated to program in rust this way in 2024.

[progbits]

I use it together with VS code and rust-analyser. I like having a view of the entire project - if I break something in a file I don't have open in the editor it is more obvious in the bacon output. You can also switch it to test mode.

However compared to cargo watch -c -x {check,test} it is only marginal improvement.

[norman784]

One issue I'm having with bacon, that's why I don't use if often, is that after a while it seems that it stop working, I need to restart so it would run after a project file changes, also I use most of the time cargo watch.

[ranguna]

If you open the "problems" menu in the bottom bar (a tab on the same menu as the terminal), you should see all the error for your whole project.

[bobbylarrybobby]

I agree, bacon doesn't seem significantly different from the VSCode problems pane — which also hyperlinks to the locations in question — except perhaps the way problems are sorted between the two.

[earthling8118]

It isn't outdated. I run lsp and bacon when working. You can get bacon to run clippy for you, which is also really good to use.