News for hackers. Stuff that matters.
Re:What it feels like when Rust saves your bacon by jackmott42 on Friday June 24, 2022 @10:33AM (#31862545)
I'm sure there is a ton of variance. I have done some Rust projects where I run into absolutely no safety complaints from Rust because it just isn't the kind of code that does anything the borrow checker cares about. For those development time ends up typically faster than C/C++ due to various syntax and tooling niceties.

Other projects will really get into domains where you have to work hard to satisfy the borrow checker and it can slow you down a lot. In a real application you won't be writing lockless thread queues for a big % of the time. But then for a real application the compile times will start to weigh on you more. (Though, C++ does not always compile fast either unless some care is taken to be sure it does)

Re:What it feels like when Rust saves your bacon by ttfkam on Saturday June 25, 2022 @10:52AM (#31875761)
And you're running at least one static analysis tool and a linter on your C++ code too, right? You're not just deploying the C++ compiler output as-is, right?

Those take time to run too and should absolutely be added to the compile time metrics when comparing against "cargo build".

Re:What it feels like when Rust saves your bacon by jesse__ on Saturday June 25, 2022 @11:12AM (#31875911)
On a personal project I run 2 metaprogramming passes, compile the entire project (~2m LoC) _twice_ and run the entire test suite in < 30s on a laptop from 2010.

I don't run a linter because I hate them, and my metaprogramming passes do a bit of extra static checking clang doesn't. I occationally run extra static tools (valgrind et. al) but they're painfully slow and very rarely catch anything.

Re:What it feels like when Rust saves your bacon by kaba0 on Saturday June 25, 2022 @01:37PM (#31877123)
Rust in incremental build mode is not slow at all, I really don’t see why people say so.