rt-write-lock 0.1.0

concurrent, realtime write data structure
Documentation
  • Coverage
  • 11.11%
    1 out of 9 items documented0 out of 8 items with examples
  • Size
  • Source code size: 351.83 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.7 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 11s Average build duration of successful builds.
  • all releases: 11s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Repository
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • luca3s

Realtime write lock

This is a concurrent, realtime data structure. The write locking is always nonblocking, while read locking may block. It is useful for communicating data from a realtime thread (for example the audio thread) to a non realtime thread (for example the GUI thread). The Data should always be replaced completely, not updated incrementally.

If the writer thread is the non realtime thread and reading should be nonblocking take a look at my other library simple-left-right. The implementation is similar, but the roles are reversed.

Hosted on tangled, codeberg and github. Open a PR or issue on any platform you like.

std::mem::forget

The library tries to detect if a Read/Write guard is forgotten and panics. Without this detection this could lead to UB.