9 releases (4 breaking)

0.5.0 Oct 24, 2021
0.4.1 Jul 3, 2021
0.4.0 May 9, 2021
0.3.1 May 4, 2021
0.1.0 Apr 3, 2021

#34 in Memory management

Download history 81/week @ 2021-10-05 70/week @ 2021-10-12 47/week @ 2021-10-19 51/week @ 2021-10-26 92/week @ 2021-11-02 68/week @ 2021-11-09 71/week @ 2021-11-16 22/week @ 2021-11-23 162/week @ 2021-11-30 80/week @ 2021-12-07 77/week @ 2021-12-14 65/week @ 2021-12-21 73/week @ 2021-12-28 48/week @ 2022-01-04 72/week @ 2022-01-11 119/week @ 2022-01-18

336 downloads per month


1.5K SLoC

StaticRc is a safe reference-counted pointer, similar to Rc or Arc, though performing its reference-counting at compile-time rather than run-time, and therefore avoiding most run-time overhead.

Motivating Example

A number of collections, such as linked-lists, binary-trees, or B-Trees are most easily implemented with aliasing pointers.

Traditionally, this requires either unsafe raw pointers, or using Rc or Arc depending on the scenario. A key observation, however, is that in those collections the exact number of aliases is known at compile-time:

  • A doubly linked-list has 2 pointers to each node.
  • A binary-tree has 3 pointers to each node: one from the parent, and one from each child.
  • A B-Tree of cardinality N has N+1 pointers to each node.

In this type of scenario, static-rc offers the safety of Rc and Arc, with the performance of unsafe raw pointers.


Provide safe and efficient reference-counting:

  • Efficiency: most associated functions boil down to copying a NonNull<T>, a trivial operation.
    • One key exception are join functions: a run-time check must be performed to ensure the instances being joined refer to the same pointer. Unsafe unchecked variants are available if their overhead is too high.
  • Safety: most associated functions are safe to use.
    • The few unsafe functions are strictly optional.


This crate is still very much experimental.


  • Minimally reviewed.
  • Not audited.
  • Not formally proven.


  • All StaticRc associated functions are documented, with example.
  • All StaticRcRef associated functions are documented, with example.


  • All compile-time assertions are tested with compile-fail tests.
  • All panics are tested with panic tests.
  • Miri runs the test-suite without any complain.

Debug checks

This library contains a number of additional checks when building with debug_assertions, in particular the Drop implementation of StaticRc will catch any attempt at destroying a StaticRc<T, N, D> where N <> D, as this would typically result in a leak.

Those checks are not strictly necessary for safety, they are included to help point out logic errors.

From experience, the Drop check on top of an extensive test-suite will help catch all those instances where one path accidentally let a pointer drop.

That's all folks!

And thanks for reading.

No runtime deps


  • alloc
  • compile-time-ratio
  • experimental-lift
  • nightly-async-stream
  • nightly-coerce-unsized
  • nightly-dispatch-from-dyn
  • nightly-generator-trait