Post ApysitBcmPcN9aUB3g by cerberus1746@mastodon.gamedev.place
(DIR) More posts by cerberus1746@mastodon.gamedev.place
(DIR) Post #ApyQ0TFp2LXvGfTrBQ by BrodieOnLinux@mstdn.social
2025-01-11T13:13:58Z
0 likes, 1 repeats
Say it with me everyone:Rust memory leaks are memory safe
(DIR) Post #ApyQV9ZQGrMNCFHMnY by phil0x2e@bonn.social
2025-01-11T13:19:24Z
0 likes, 0 repeats
@BrodieOnLinux aren't memory leaks always "safe"? It's just memory that's not freed after it's not needed anymore.What's not safe are use-after-frees and out of bounds writes etc.
(DIR) Post #ApyR3K1JvO9bS6cYKm by grishka@friends.grishka.me
2025-01-11T13:25:40Z
0 likes, 0 repeats
Are Rust segfaults also memory safe?
(DIR) Post #Apydiwe6Q4cKZPNI9I by decathorpe@mastodon.social
2025-01-11T15:47:38Z
0 likes, 0 repeats
@BrodieOnLinux is this bait? ๐
While memory leaks are undesirable in almost all cases, they are "safe" - just because they don't cause memory access patterns that are, indeed, "unsafe" (use-after-free, double-free, reading uninitialized memory, unsynchronized read/writes to shared memory, etc.)And the quotes around "safe" and "unsafe" are intentional - because those words have specific meaning in the Rust context ... (probably the source of much of the confusion around these terms wrt/ Rust)
(DIR) Post #Apyezj725bkJTSTMJM by TornaxO7@mastodon.social
2025-01-11T16:01:43Z
0 likes, 0 repeats
@BrodieOnLinux may I ask what your intention is? Maybe I'm missunderstanding it, but I read it in a passive aggressive tone.
(DIR) Post #ApysitBcmPcN9aUB3g by cerberus1746@mastodon.gamedev.place
2025-01-11T18:35:42Z
0 likes, 0 repeats
@BrodieOnLinux I had to triple read the post to understand it.
(DIR) Post #ApzAEnTDGbcNucVsfI by BrodieOnLinux@mstdn.social
2025-01-11T21:51:59Z
0 likes, 0 repeats
@decathorpe Whenever I talk about a memory leak in COSMIC people always say "But I thought Rust was memory safe"
(DIR) Post #ApzDHsFOGJA9SXCsBE by decathorpe@mastodon.social
2025-01-11T22:26:04Z
0 likes, 0 repeats
@BrodieOnLinux ah, so one more example of "YouTube commenters don't know what they're talking about"? ๐
(DIR) Post #Aq1AjJvZXn9Na4Fiz2 by nobloat@fosstodon.org
2025-01-12T21:06:53Z
0 likes, 0 repeats
@BrodieOnLinux I did some C and I am currently learning Rust. What I find interesting is how the design of the language forces you to write safer code, not just when it comes to memory but it forces error handling more than other languages. The Option and Result enums are really great from I've seen so far. The Option enum makes it so that the Null is not needed anymore. Many design decisions have been made to make you write safer code without sacrificing performance.