hmm, very on the fence about using polymorphism vs making it explicit that Rc::clone(&foo) copies a pointer vs foo.clone(), which, uh, might do anything, idk?
-
"retain" means you're creating a new ref and the old one should "retain" its refcount, so you increment the refcount. C++ refcount libs often interface with raw ptrs (and often use intrusive refcounting) so this terminology is more common, but it sometimes crops up for rust
I know it from pre-arc objective C which is the only other time I've ever worked with explicit reference counting
-
-
I just sorta assumed it was standard terminology
-
it is! it's just not as used in rust because moves handle adoption (so retain is the only thing that happens explicitly) and only time you need to worry about "adopt" is when you're interfacing with raw pointers (rare)https://github.com/retep998/wio-rs/issues/20 …
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.