Crates.io | implicit-clone |
lib.rs | implicit-clone |
version | 0.5.0 |
source | src |
created_at | 2022-04-15 07:36:09.189311 |
updated_at | 2024-07-12 20:06:42.866028 |
description | Immutable types and ImplicitClone trait similar to Copy |
homepage | https://github.com/yewstack/implicit-clone |
repository | https://github.com/yewstack/implicit-clone |
max_upload_size | |
id | 568281 |
size | 59,656 |
This library introduces the marker trait ImplicitClone
intended for
cheap-to-clone types that should be allowed to be cloned implicitly. It enables host libraries
using this crate to have the syntax of Copy
while actually calling the
Clone
implementation instead (usually when host library does such syntax
in a macro).
The idea is that you must implement this trait on your cheap-to-clone types, and then the host library using the trait will allow users to pass values of your types and they will be cloned automatically.
Standard types that the ImplicitClone
is already implemented for:
std::rc::Rc
std::sync::Arc
ImplicitClone
Option
, where inner value is ImplicitClone
Copy
types, like ()
, bool
, &T
, etc.This crate is in the category rust-patterns
but this is actually a Rust anti-pattern. In Rust
the user should always handle borrowing and ownership by themselves. Nevertheless, this pattern
is sometimes desirable. For example, UI frameworks that rely on propagating properties from
ancestors to multiple children will always need to use Rc
'd types to cheaply and concisely
update every child component. This is the case in React-like frameworks like
Yew.
This crate also provides a few convenient immutable types for handling cheap-to-clone strings,
arrays and maps, you can find them in the modules sync
and
unsync
. Those types implement ImplicitClone
and
hold only types that implement ImplicitClone
as well. One big
particularity: iterating on these types yields clones of the items and not references. This
can be particularly handy when using a React-like framework.