armanriazi•rust•type•wrapper•vs•clone

ArmanRiazi answered on March 9, 2022 Popularity 1/10 Helpfulness 1/10

answer armanriazi•rust•type•wrapper•vs•clone

armanriazi•rust•type•wrapper•vs•clone

Comment

If implementing Clone would be prohibitively expensive, Rc<T> can be a handy alternative. This allows two places to “share” ownership.
We could have called a.clone() rather than Rc::clone(&a), but Rust’s convention is to use Rc::clone in this case. The implementation of Rc::clone doesn’t make a deep copy of all the data like most types’ implementations of clone do.
The call to Rc::clone only increments the reference count,
which doesn’t take much time. Deep copies of data can take a lot of time.
By using Rc::clone for reference counting, we can visually distinguish between the deep-copy kinds of clones and the kinds of clones that increase the reference count

Popularity 1/10 Helpfulness 1/10 Language rust

Source: github.com

Tags: rust

Link to this answer
Share Copy Link

Contributed on Mar 09 2022

ArmanRiazi

0 Answers Avg Quality 2/10

armanriazi•rust•type•wrapper•vs•clone

Contents

More Related Answers

armanriazi•rust•type•wrapper•vs•clone

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.