clone_from 0.1.0

Derive Clone including clone_from
Documentation
  • Coverage
  • 50%
    1 out of 2 items documented0 out of 1 items with examples
  • Size
  • Source code size: 20.13 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 278.36 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 4s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • antiguru/clone_from
    8 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • antiguru

Derive Clone including clone_from

This crate offers a derive macro called CloneFrom to derive Clone with a specialized clone_from implementation.

When deriving Clone, Rust omits a specialized clone_from implementation and defers to clone instead. This means that it can behave counter-intuitively, for example when it should reuse allocations, but does not. This crate aims to be a drop-in replacement for deriving Clone, but with a proper clone_from implementation.

Example

#[derive(CloneFrom)]
struct MyStruct<T> {
    name: String,
    inner: Vec<T>,
}

Considerations

Adding a clone_from implementation to all types in Rust seems to add a significant compile-time cost, which is why Rust does not provide this by default. Many types do not benefit from a specialized clone_from implementation, so it's important to add it when it brings a benefit.

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.