archery
archery copied to clipboard
orium
Abstract over the atomicity of reference-counting pointers in rust
Looking at the API of [`StaticRc`](https://docs.rs/static-rc/latest/static_rc/rc/struct.StaticRc.html) and [`SharedPointerKind`](https://docs.rs/archery/0.4.0/archery/shared_pointer/kind/trait.SharedPointerKind.html) I think it would be possible to add support for `static-rc` behind a feature flag. What do you think?
Thanks for your work on this crate! Are there any plans to support Weak pointers?
Updates the requirements on [criterion](https://github.com/bheisler/criterion.rs) to permit the latest version. Changelog Sourced from criterion's changelog. [0.4.0] - 2022-09-10 Removed The Criterion::can_plot function has been removed. The Criterion::bench_function_over_inputs function has been...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
I don't yet know enough to be able to determine whether this would break invariants that must be upheld. Would it be possible & feasible to do this so that...
https://github.com/orium/archery/blob/49ba594bf19b92c912135c7c7e6dad37961c3867/src/shared_pointer/kind/arc/mod.rs#L8 This won't compile under architecture that does not support atomic instructions such as `riscv32imc-unknown-none-elf`. But on a higher level of thoughts this means the entire Arc/ArcK should be disabled
