25 releases

0.6.1 Jun 6, 2024
0.5.4 Apr 26, 2024
0.5.2 Mar 22, 2024
0.5.1 Jun 24, 2023
0.2.0 Nov 4, 2016

#104 in Rust patterns

Download history 16137/week @ 2024-03-01 19251/week @ 2024-03-08 17414/week @ 2024-03-15 18129/week @ 2024-03-22 18683/week @ 2024-03-29 18374/week @ 2024-04-05 16507/week @ 2024-04-12 18098/week @ 2024-04-19 16918/week @ 2024-04-26 16061/week @ 2024-05-03 18454/week @ 2024-05-10 16259/week @ 2024-05-17 16529/week @ 2024-05-24 15832/week @ 2024-05-31 14186/week @ 2024-06-07 15082/week @ 2024-06-14

64,079 downloads per month
Used in 85 crates (23 directly)

MIT/Apache

57KB
800 lines

volatile

Build Status Docs.rs Badge

Provides volatile wrapper types for raw pointers.

The volatile wrapper types in this crate wrap a pointer to any Copy-able type and provide volatile memory access to wrapped value. Volatile memory accesses are never optimized away by the compiler, and are useful in many low-level systems programming and concurrent contexts.

This crate provides two different wrapper types: VolatilePtr and VolatileRef. The difference between the two types is that the former behaves like a raw pointer, while the latter behaves like a Rust reference type. For example, VolatilePtr can be freely copied, but not sent across threads because this could introduce mutable aliasing. The VolatileRef type, on the other hand, requires exclusive access for mutation, so that sharing it across thread boundaries is safe.

Both wrapper types do not enforce any atomicity guarantees; to also get atomicity, consider looking at the Atomic wrapper types found in libcore or libstd.

Why is there no VolatileCell?

Many people expressed interest in a VolatileCell type, i.e. a transparent wrapper type that owns the wrapped value. Such a type would be similar to core::cell::Cell, with the difference that all methods are volatile. Unfortunately, it is not sound to implement such a VolatileCell type in Rust. The reason is that Rust and LLVM consider & and &mut references as dereferencable. This means that the compiler is allowed to freely access the referenced value without any restrictions. So no matter how a VolatileCell type is implemented, the compiler is allowed to perform non-volatile read operations of the contained value, which can lead to unexpected (or even undefined?) behavior. For more details, see the discussion in our repository and in the unsafe-code-guidelines repository.

License

Licensed under either of

at your option.

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

Dependencies

~115KB