Notices by Fabio Valentini (decathorpe@mastodon.social)

@BrodieOnLinux if you count thread safety too (Rust does), then Go, Java, and Python are not entirely "safe" either (but apparently the latest Swift is)

@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)

@aral @ceremus Yeah ... this time it was flagged by an actual person, and your post was hidden by a moderator for being "off-topic". I don't understand nor do agree with this assessment, but I don't want to just override another moderator's decision here, either 😐

@aral @JoshStrobl This is what I see as a moderator ... I pushed the button to approve it, so it should be visible now.

(potentially toxic, accuracy: 11% does not inspire confidence in that automatic classification though)