Conversation
Notices
-
† top dog :pedomustdie: (dcc@annihilation.social)'s status on Thursday, 30-Jan-2025 06:15:46 JST † top dog :pedomustdie:
Rust mem eror'd....
thread 'tokio-runtime-worker' panicked at src/player.rs:97:55:
called `Option::unwrap()` on a `None` value
I THOUGH IT WAS MEMEORY SAFE SAAR :troll:-
nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Thursday, 30-Jan-2025 06:17:34 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
@dcc yeah it stopped you from dereferencing null, and told you where it was doing it from, quite helpful actually. in C it would've just told you "Segmentation Fault" and left you to eat shit -
† top dog :pedomustdie: (dcc@annihilation.social)'s status on Thursday, 30-Jan-2025 06:18:07 JST † top dog :pedomustdie:
@nyanide I did not do anything lol, thats the code the inv thing uses. -
Phantasm (phnt@fluffytail.org)'s status on Thursday, 30-Jan-2025 06:18:26 JST Phantasm
@dcc Never talk about std::mem::forget to Rust evangelists. † top dog :pedomustdie: likes this. -
nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Thursday, 30-Jan-2025 06:18:49 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
@dcc you may want to report this as a bug -
† top dog :pedomustdie: (dcc@annihilation.social)'s status on Thursday, 30-Jan-2025 06:19:24 JST † top dog :pedomustdie:
@nyanide I'm not making a git hub acount lol, we will see if it happens again. -
nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Thursday, 30-Jan-2025 06:19:35 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
@phnt @dcc what's so bad about it -
Phantasm (phnt@fluffytail.org)'s status on Thursday, 30-Jan-2025 06:23:31 JST Phantasm
@nyanide @dcc It leaks memory, something _some_ Rust programmers refuse to acknowledge that Rust can do.
To be more precise it takes ownership of the argument and forgets it without running it's destructor.
By it self it's basically harmless as you have to call it manually, but it could possibly be leveraged to force a specific heap order that you can then exploit if you find a way to break out of the Rust bounds checking. The chance of this getting exploited in the future is near zero. -
Phantasm (phnt@fluffytail.org)'s status on Thursday, 30-Jan-2025 07:03:48 JST Phantasm
@mr64bit @dcc @nyanide It's been a long time since I saw someone like this. They seemingly mostly went away after the rewrite in Rust meme died out. Recently it's mostly people that actually write Rust trying to force Rust onto other projects, because muh memory safety and other stuff.
The last time I had any kind of discussion with someone that could be described as a Rust evangelist was during the Lina Linux drm threads. It was about why Rust shouldn't be used in Linux due to its non-existent ABI and other related stuff. They deleted their replies a few days after for whatever reason.
But I still like to shitpost about Rust every once in a while, because somehow barely funny posts make them react every time. That includes today's posts.
In the end, I don't have a problem when a project is written in it, but I still stand by my opinion that it shouldn't be used for low-level programming. It's just not a language for it. There's no stable ABI, interacting with Rust code outside of Rust is painful, static-linking everything is stupid and cargo is borderline garbage. -
mr64bit (mr64bit@p.mr64.net)'s status on Thursday, 30-Jan-2025 07:03:49 JST mr64bit
@phnt @dcc @nyanide I'm convinced there's basically no overlap between the rust evangelists everyone complains about and people who actually write rust. Then again, I never see the evangelists either, seems be a strawman for the most part. -
ins0mniak (ins0mniak@majestic12.airforce)'s status on Thursday, 30-Jan-2025 07:04:01 JST ins0mniak
@phnt @dcc @nyanide @mr64bit -
Phantasm (phnt@fluffytail.org)'s status on Thursday, 30-Jan-2025 07:08:14 JST Phantasm
@ins0mniak @dcc @nyanide @mr64bit You probably don't use Arch, or know about it's "drama", but literally the only reason why paru, the AUR helper, was created, is because the creator of yay, written in Golang, and a co-maintainer of it had a dispute over why it should be rewritten in Rust.
To this day they are mostly the same minus the language used.† top dog :pedomustdie: likes this. -
Phantasm (phnt@fluffytail.org)'s status on Thursday, 30-Jan-2025 07:59:23 JST Phantasm
@mr64bit @dcc @nyanide By low-level I mean things like kernels, bootloaders, base system libraries and such. Systems programming is probably a better word for that.
It's fine for writing userspace applications, not so much for libraries that other non-Rust programs would like to use (the equivalent of glibc and similar). That makes it essentially almost useless everywhere but at the end of the whole software chain. Nothing but Rust code can interact with it without breaking easily.† top dog :pedomustdie: likes this. -
mr64bit (mr64bit@p.mr64.net)'s status on Thursday, 30-Jan-2025 07:59:24 JST mr64bit
@phnt @dcc @nyanide ah, guess I'd forgotten about the 'rewrite it in rust' crazyness. I've never had problems doing low-level stuff with it, but maybe it helps that a lot of my use cases are pretty unorthodox. I agree about cargo, definitely my biggest complaint. rust may be a systems programming language, but cargo is by no means systems programming build system.
-