3 ms·
But if I'm not mistaken, this is just handling index allocation, release and avoiding dangling manually. The programmer is still responsible, right? And I don't
by tgv 8mo ago
But if I'm not mistaken, this is just handling index allocation, release and avoiding dangling manually. The programmer is still responsible, right? And I don't think Rust can do better for indices, since indices are normal, "eternal" values.
- fooker 8mo ago> this is just handling index allocation, release and avoiding dangling manually No, it is abstracted away. You just have to follow best practices when writing a library. resource foo(...); // This gets freed at the end of scope. See RAII. auto x = make_unique<resource>(...); // can be moved, freed when owner is. auto y = make_shared<resource>(...); // freed on zero reference count