2 ms·
Oh, there are plenty of idioms you can use in C++ that are easy to make safe (as long as you don't make a mistake on some very small amount of code) that Rust w
by marcosdumay 4y ago
Oh, there are plenty of idioms you can use in C++ that are easy to make safe (as long as you don't make a mistake on some very small amount of code) that Rust will make a nightmare to implement.
Just like there are plenty of idioms you can use in Haskell that are easy to make simple that Rust will make a nightmare to implement.
At the end of the day, Rust is neither of those. It is a safe low level language, and that comes with plenty of restrictions. The language is amazing for how little restrictions it actually has when compared to a naive estimate, but there are still plenty of them.
- zozbot234 4y agoThe problem is that very few idioms are both safe and compositional (which you need if you want your development approach to scale to the largest projects). Rust focuses on these as a sensible default, for everything else there's unsafe.
- Ygg2 4y ago> Oh, there are plenty of idioms you can use in C++ that are easy to make safe (as long as you don't make a mistake on some very small amount of code) that Rust will make a nightmare to implement Like? I know double linked lists and graphs are harder to get right, but aren't impossible. But on the flip side getting Optional and Send/Sync to work in C/C++ and not to rely on people using best practices is downright impossible.