The borrow checker is a feature of Rust’s compiler which places strict constraints on ownership of data to guarantee memory safety. It adds a lot of friction to writing Rust code if you’re not experienced with the language (or sometimes even if you are). OP refers to the “language restriction of Rust”, seemingly talking about the borrow checker, but has never even heard of it. It’s kind of like someone claiming they didn’t vibecoded their C++ project but having no idea what the STL is.
- 0 Posts
- 8 Comments
That was obviously a joke though, and it wasn’t even OP.
YaBoyMax@programming.devto
Programmer Humor@programming.dev•C++ takes decades to masterEnglish
5·4 months agoI don’t disagree that the language is a great way to build an understanding of object lifecycles, but in my experience C++ ctors and dtors are also the biggest source of confusing footguns I’ve ever encountered in any programming language.
Separately, template metaprogramming is a whole different beast. It’s an extremely powerful tool, but to me it also feels like finding the correct incantation to get it to do exactly what you need for more complex scenarios. It can be really fun if you know what you’re doing, but it also tends to make me very upset at the compiler when my incantations are a bit off.
YaBoyMax@programming.devto
Programmer Humor@programming.dev•holy shit holy shit holy shit holyEnglish
7·6 months agoYeah, it’s not grammatically correct AFAIK but it’s a fairly common mistake to see.
YaBoyMax@programming.devto
Linux@lemmy.ml•Which of the 3 standard compression algorithms on Unix (gz, xz, or bz2) is best for long term data archival at their highest compression?English
21·1 year agoUnrelated, but what on earth is going on with the thorns in your comments?
YaBoyMax@programming.devto
Linux@lemmy.ml•Which of the 3 standard compression algorithms on Unix (gz, xz, or bz2) is best for long term data archival at their highest compression?English
8·1 year agoAFAIK none of those formats include any mechanism for error correction. You’d likely need to use a separate program like zfec to generate the extra parity data. Bzip2 and Zstandard are somewhat resistant to errors since they encode in blocks, but in the event of bit rot the entire affected block may still be unrecoverable.
Alternatively, if you’re especially concerned with robustness then it may be more advisable to simply maintain multiple copies across different drives or even to create an off-site backup. Parity bits are helpful but they won’t do you much good if your hard drive crashes or your house catches fire.
Interpreting a PR which changes “he” to “they” as pushing political ideology is not an apolitical stance. I don’t know a ton about him and I’m not convinced this makes him a “fascist” by association, but the fact that he seems to be ideologically aligned with the ones in power on America is troubling at the very least.
On the contrary, the borrow checker is basically the first thing you learn about when writing in Rust as it’s the primary “gimmick” of the language. Anyone writing a non-trivial program should have at least heard the term before, even if they don’t fully understand how it works.