#sync #thread

macro inert_derive

See the inert crate

5 releases

✓ Uses Rust 2018 edition

0.1.4 Mar 19, 2019
0.1.3 Mar 12, 2019
0.1.2 Mar 8, 2019
0.1.1 Mar 6, 2019
0.1.0 Feb 25, 2019

#148 in Concurrency

38 downloads per month
Used in 1 crate

Apache-2.0 OR MIT

195 lines


This is a mechanism to access non-Sync values in a Sync way.

How is this sound?

When the user creates a &Inert<T> value from a &T, they must swear on the holy baguette that they won't use the T directly until all the Inert wrappers go away, while the various implementations of the NeutralizeUnsafe trait make sure that the non-Sync behaviour of the T cannot be observed through the wrapper.

How can I help?

Improve documentation, test the crate, make use of it.


~17K SLoC