30
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Apr 2024
30 points (78.8% liked)
Open Source
31088 readers
735 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
Can you share what would be a concrete example of the risk taken by running a RM program with a memory leak or dangling pointers? I fail to see, by my own ignorance, the benefit of memory safety everywhere. But I do enjoy the rust rewrites of shell tools because of the ergonomics, speed, and new functionalities. I'm asking because the first thing you mentioned as a benefit was memory safety.
This probably isn't the answer you're looking for, but
vpr
being memory-safe isn't a benefit that it has overrm
, sincerm
apparently doesn't allocate any memory (as @radiant_bloom@lemm.ee wrote).Looks like I worded my project description poorly. As I wrote in another comment, I meant that this alternative is memory-safe (being written in safe Rust), but not that
rm
isn't.edit: I've updated the post's title to clear things up