You must log in or register to comment.
Just add
unsafesheesh.best solution to all rust problems /s
This might be the wrong place for this question, but I have heard criticism that real rust programs contain lots of unsafe code. Is this true?
Define what makes a rust program “real” lol.
Any kind of library that does a lot of low-level stuff (kernel syscalls, custom binary reprs, ffi) will have to use unsafe. But most applications built using these libraries rarely need to use unsafe at all, because the libraries act as safe wrappers to make sure the app developer isn’t accidentally violating invariants allowed by the “unsafe” keyword.
Yeah. For example Lemmy backend is written purely in Rust and doesn’t use unsafe anywhere, but some lower-level library it uses probably does use unsafe for IO code.
Just use make-static, no unsafety in sight.
That’s clever. I lol’d
I’m definitely missing something here. I’m terrible at rust and c++
The meme refers to the old adage “C lets you shoot yourself on the foot. C++ lets you shoot both feet and gives you a shotgun to do it” - referring to the how C allows you to perform memory-unsafe operations (causing corruption, or worse, security vulnerabilities), and C++'s complexity, potentially obscuring such unsafetyness.
Rust’s memory safety tries to save you from doing (un)intentional bad stuff, by giving you compile-time errors. It’s also the bane of everyone so used to C/++'s ability to just pass around and modify whatever memory they want.
I’ve actually never heard that one before. I was specifically referencing this quote by the language’s creator, but I guess that one works too.
What you are missing, of course, is the
Rc<Refcell<T>>that you have to stick everywhere to make a nontrivial Rust program. It’s like monads in Haskell, parentheses in lisp, verbosity in Java, or warnings in C - they’re the magic words you have to incant correctly to make things work in their weird paradigms.deleted by creator
