this post was submitted on 01 Nov 2023
139 points (96.0% liked)

Programming

17111 readers
308 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

Assume mainstream adoption as used by around 7% of all github projects

Personally, I'd like to see Nim get that growth.

you are viewing a single comment's thread
view the rest of the comments
[–] IAm_A_Complete_Idiot@sh.itjust.works 9 points 11 months ago (10 children)

Rust doesn't guarantee the lack of memory leaks anymore then java/C++ does, so sadly not sure if it would help here. :)

[–] Rin@lemm.ee 1 points 11 months ago (7 children)

Help me understand your point of view. How does Rust not prevent memory leaks?

[–] IAm_A_Complete_Idiot@sh.itjust.works 18 points 11 months ago (6 children)

There's built in functions to leak memory that are perfectly safe. You can also do one really trivially by making a reference count cycle. https://doc.rust-lang.org/book/ch15-06-reference-cycles.html

Rust only prevents memory unsafety - and memory leaks are perfectly safe. It's use after frees, double frees, etc. It prevents.

[–] hairyballs@programming.dev 9 points 11 months ago

And here you're only talking about a subset of memory leaks, by inaccessible memory. You can also leak memory by pushing new elements in a channel while never reading them for example.

load more comments (5 replies)
load more comments (5 replies)
load more comments (7 replies)