Re:Rust means never having to close a socket
by shadowmint on Tuesday October 07, 2014 @11:02PM
(#8425131)
> It is nonsense to say that "libraries can have bugs so you might as well use C++".
My argument is that if you assert 'rust is 100% safe' then you must assert, all your dependencies are bug free.
If you can somehow magically assert 'all my code is bug free', that would be great... but if so, you wouldn't need the borrow checker at all would you?
(I'm certainly not endorsing using C++ :P I'm specifically talking to the assertion that rust code can be safe, as per the definition of safety in the guide, that certain operations are impossible; certainly, and absolutely, rust code is safer and more trust worthy (imo) than c/c++ code... but you've got to be reasonable about what you're arguing. 'rust is magical and can never crash' turns up in blog posts a lot)
Of course it's not true, but the libraries you're using will (hopefully, for the most part) be written in Rust, which increases the level of trust.
> There's a trust chain involved; if you depend on a library you trust it's bug free and won't delete your harddisk and crash your program, but there's a difference between trusting a library is not malicious, and trusting a library is bug free.
> If you have to trust the library is bug free, you're really no better off than using C++ are you?
The libraries are written in Rust, so have all the benefits of that. It is nonsense to say that "libraries can have bugs so you might as well use C++".