this post was submitted on 22 Jul 2025
21 points (100.0% liked)

Rust

7602 readers
67 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
21
Alternative Ergonomic Ref-counting RFC (github.com)
submitted 5 months ago by SorteKanin@feddit.dk to c/rust@programming.dev
3 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] balsoft@lemmy.ml 5 points 5 months ago* (last edited 5 months ago)

Otherwise, the keyword use seems too generic to be used for this

I also feel that way, and I don't even understand how the word "use" is related to the underlying semantics at all.

My only guess is that use is already a keyword, and anything that's not a keyword currently would require a new language edition. I would also prefer something like autoclone async {}, or maybe even with_cloned <explicit list of objects to clone, or _ for automatic detection> async {} . Not sure if it 100% makes sense but would be more readable IMO.

P.S. it seems they will explore an alternative solution that doesn't involve a new keyword at all, and just automagically clones when it's "cheap" to do. Sounds more user-friendly to me TBH.