Bacon – a background Rust code checker
dystroy.org
Bacon – a background Rust code checker
1–10 of 14 posts
Re: Bacon – a background Rust code checker
#2I 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.
Re: Bacon – a background Rust code checker
#3I 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 t…
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.
Re: Bacon – a background Rust code checker
#4I'd have assumed that using a language server would avoid the need for using something like this, but as a frequent user of ibazel (sort of inotify-watch+make for bazel) I can see how this can be enough to get productive without an editor that fully supports LSP
Re: Bacon – a background Rust code checker
#5I 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 t…
[deleted]
Re: Bacon – a background Rust code checker
#6I 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 t…
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.
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.
Re: Bacon – a background Rust code checker
#7I 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 t…
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.
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.
Re: Bacon – a background Rust code checker
#8[flagged]
Re: Bacon – a background Rust code checker
#9Working on an OS in Rust, rust-analyzer chokes. A _lot_. I end up just having to run a compilation to see what I've broken.
Haven't tried it yet but it looks like it'll be an invaluable part of my toolbox. Thanks for posting this!
Re: Bacon – a background Rust code checker
#10I 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 t…
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.