expiring_ref 0.7.0

A crate designed to implement a mechanism for owning values, via a destructively-moved equivalent to C++'s xvalues/`T&&`

Documentation

Coverage
25.93%
7 out of 27 items documented0 out of 23 items with examples
Size
Source code size: 18.58 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 900.76 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: 10s Average build duration of successful builds in releases after 2024-10-23.
Links
Repository
crates.io
Dependencies
Versions
Owners

expiring_ref

Crates.io Version

A crate designed to implement a mechanism for owning values, via a destructively-moved equivalent to C++'s xvalues/T&&

Previously known as ownership_traits before being reworked to implement owned references.

crates.io page: https://crates.io/crates/expiring_ref Source code: https://git.gay/Zepalesque/expiring_ref

NOTE

The expiring_ref crate follows an unconditional anti-LLM and anti-gen-AI policy for all contributions. Vibe coding sucks for everyone, don't do it.