It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path
Technically you need a separate linter (errcheck) to ensure you don't just ignore errors. This is...not great. (That should have been a compiler error.)
Delete prior iterations of the loop in the same timeline? I'm not sure there's anything in quantum mechanics to permit that...
The O'Reilly book Programming Rust is very much targeted at C++ users, even if it isn't explicitly marketed that way.
I read the first edition, which predated async Rust, so I can't comment on how the second edition handles that topic. But the handling of everything else was, I think, excellent.
To be pedantic, I didn't ask a question, I just said I was surprised! I am still surprised.
Yes. True. But Uncle Bob literally complains about non-nullable types in the linked blog post.
I'm not saying testing isn't important. I'm saying that hand-written unit tests are not the end-all be-all of software quality, and that Uncle Bob explicitly believes they are.
C is in no way "more for hobby developing and tooling". It's still foundational to compilers, language runtimes, and operating systems (the Linux kernel was, famously, exclusively written in C up until extremely recently, and the non-C parts are still optional). It's also the only supported language on many embedded devices.
the author in his 11y of writing Rust never once heard about the philosophy of Rust/Unsafe Rust.
Are you...aware of who the author is? He literally co-wrote The Book, aka The Rust Programming Language.
The standard differentiates between "unspecified" behavior, which is as you describe, and "undefined" behavior, which may be completely nondeterministic at runtime.
The CLI is still pretty bad, and I say this as someone who's gotten so used to it that I find git GUIs more annoying than helpful.
log gets a random flag from diff, -p, that's incredibly useful but buried in the documentation. Printing a readable graph log requires magic incantations that aren't worth memorizing. git branch with no subcommand prints the list of branches, but to get similar behavior for git remote, you need to add -v. Etc.
I'm not sure where you're quoting from, but as far as I can see, only "Professional Engineer", "Licensed Engineer", and "Registered Engineer" are protected in the US.
Wow, of course he's pretending the response is a misrepresentation of his opinion instead of defending it in good faith.
Notably, this article is from 2014.