Triple buffering in Rust weaknesses?

Regarding:

Triple buffering in Rust

https://crates.io/crates/triple_buffer

It seems to me all it weaknesses are pointing out overhead that exists regardless, albeit in different form. Is this true?

I mean the copies, clones and raw functions re ownership that are unavoidable in transitioning back to safe code.

For small messages, an additional abstraction gives an ARC of producers and he already multithreaded the consumers else where.

One consumer owned bit (bool?) solves all his other complaints without error or lag. Zero cost. Dirty reads being harmless.

It acts like LAN traffic to me given the collisions.

Oops two bits.

  1. Locked.
  2. Done.

There is lag too. My mistake. In the form of write time ns after mutex expiry.