Why so many clowns here argue that Rust lose its selling point when you use unsafe?Some cases require manual memory management and Rust acknowledge that, unsafe Rust is safer and easier to debug than C\C++, your codebase could be 90% safe Rust and 10% unsafe Rust for performance, and in case you made a memory bug with unsafe you just need read 10% of your codebase, unlike C\C++ where you need to read the whole codebase to find memory bugs
In most software safety actually isn't something we care about at all
>vtranny>rustnot even going to read it
>>109449464unsafe zig is safer than unsafe rust
>>109449464Your code might be safe tranny but how safe is your asshole from my cock?
>>109449464because they are, as you said, clowns. can't believe I wasted so many years falling for the tranny meme
>>109449464"performance" is the worst reason for using "unsafe", and indicative of someone who is still stuck, if in part only, to C tardation, or worse, C++ tardation.
>>109449464The computer is not doing some randomly generated wizard shit, it does exactly what you tell it to do. Except when high energy cosmic particles toggle a bit but rust won't help you with that.If you write correct programs it will always do the right thing and it will be secure.The problem is that corporations want many people to write code and there aren't that many competent people and/or they are too expensive. That's why they invented rust so even retarded people who write dogshit code can be babysitted by the compiler and forced into writing secure code. By using that language outside of a corporate environment out of free will you literally stamp yourself as retarded, as they were the very reason the language came into existence in the first place. But considering the average intelligence of troons this seems to be spot on.
C isn't unsafe. You're just a retarded trannygrammer.
>>109449464unsafe Rust is actually marginally more difficult to write than C because it has more strict undefined behavior. But it doesn't matter because if you really need unsafe you probably know what you are doing and still benefit tremendously from having rest of your safe code statically checked for safety.>>109450271General purpose containers is the common place of unsafe for performance sake, but if you aren't a CS student, you very rarely need to implement one.>>109450918The reason you have types, function signatures and structures is because writing correct programs using nothing but integers and pointers is very error prone. A competent programmers can still make errors and his performance will nose dive if he needs to constantly check documentation of what register holds what at what point.Rust doesn't do anything fundamentally different than any other high level language. Just like C that has types and checks for type safety, Rust also tracks lifetimes and checks for borrows. Lifetime is just a different kind of type(literally) and borrow checker is the lifetime counterpart of a type checker.>That's why they invented rust so even retarded people who write dogshit codeThat's Go, not Rust. Rust doesn't try to be simpler or more approachable. It's rather uncompromising in terms of difficulty and that's why it filters out so many people.
