Maybe `clone_handle()` is enough to disambiguate. Though, it isn't short.

You may not have a problem with it, but it is something I see *many* software engineers working with Rust have problems with. Consider the type being cloned may not be Vec or Arc but some custom type. Being able to understand the execution behavior of code in a localized context is pretty important.

I’ve been of the belief that using clone as the main api for incrementing ref counts is not great beyond the boilerplate of cloning: it hides the complexity of the op when looking at some code in isolation. The good news is that this can be fixed in a backwards compatible way.