← Back to context Comment by galangalalgol 3 years ago This gets missed a lot. Rust isn't memory safe, it is resource safe. 5 comments galangalalgol Reply snovv_crash 3 years ago It's funny that people are assuming I was talking about Rust when I was actually referring to modern C++. RAII is a powerful concept. galangalalgol 3 years ago It is, I've written c++ as my primary language for 30 years. I skipped c++14 and I'm still using 17, but staying up to date other than that. But RAII doesn't come anywhere close to the borrow checker in the number of mistakes it prevents. hoseja 3 years ago Isn't it the other way around? galangalalgol 3 years ago My point is that it is both. The borrow-checker protects every resource, not just memory. vlovich123 3 years ago How so?
snovv_crash 3 years ago It's funny that people are assuming I was talking about Rust when I was actually referring to modern C++. RAII is a powerful concept. galangalalgol 3 years ago It is, I've written c++ as my primary language for 30 years. I skipped c++14 and I'm still using 17, but staying up to date other than that. But RAII doesn't come anywhere close to the borrow checker in the number of mistakes it prevents.
galangalalgol 3 years ago It is, I've written c++ as my primary language for 30 years. I skipped c++14 and I'm still using 17, but staying up to date other than that. But RAII doesn't come anywhere close to the borrow checker in the number of mistakes it prevents.
hoseja 3 years ago Isn't it the other way around? galangalalgol 3 years ago My point is that it is both. The borrow-checker protects every resource, not just memory. vlovich123 3 years ago How so?
galangalalgol 3 years ago My point is that it is both. The borrow-checker protects every resource, not just memory.
It's funny that people are assuming I was talking about Rust when I was actually referring to modern C++. RAII is a powerful concept.
It is, I've written c++ as my primary language for 30 years. I skipped c++14 and I'm still using 17, but staying up to date other than that. But RAII doesn't come anywhere close to the borrow checker in the number of mistakes it prevents.
Isn't it the other way around?
My point is that it is both. The borrow-checker protects every resource, not just memory.
How so?