Skip to content

Releases: HadrienG2/triple-buffer

v8.0.0

21 Jun 12:03
Compare
Choose a tag to compare

Added

  • Add Output::peek_output_buffer() method to get read-only access to the
    output buffer from a shared reference to self. Thanks @tk70!

Changed

  • Bumped MSRV to 1.74 owing to new dependency requirements.
  • Refactor CI workflow file to account for the latest GitHub CI oddities.

v7.0.0

21 Jun 12:02
Compare
Choose a tag to compare

Changed

  • Bumped MSRV to 1.70 owing to new dependency requirements.

6.2.0 - 2022-06-27

27 Jun 15:31
Compare
Choose a tag to compare

Added

  • A triple_buffer() shorthand is now available for the common TripleBuffer::new().split() pattern.

Changed

  • The documentation example now features multi-threading to clarify ownership.

6.1.0 - 2022-10-05

10 May 18:22
Compare
Choose a tag to compare

Added

  • triple-buffer is now usable in no_std contexts where an implementation of
    the alloc crate is available.

6.0.0 - 2021-12-18

18 Dec 16:01
Compare
Choose a tag to compare

Changed

  • Latest dependency versions require Rust 1.46, we bump MSRV accordingly.
  • ...and since that's a breaking change, I'm also flushing the breaking change
    pipeline along the way:
    • TripleBuffer::new now takes a reference to its input.
    • The deprecated raw feature is now removed.

5.0.6 - 2021-01-16

16 Jan 13:19
Compare
Choose a tag to compare

Added

  • As a result of the bugfix mentioned below, there is no performance motivation
    to gate raw features behind a feature flag, so those features are now
    available by default without a raw_ prefix. Usage of the raw_ prefix and
    the raw feature flag is deprecated and these may be removed in a future
    major release, but it doesn't harm to keep them indefinitely for now.

Changed

  • Benchmarks now use criterion, and have been significantly cleaned up along
    the way. They are now more extensive and more reliable.
  • Moved MSRV to Rust 1.36 because we now use crossbeam for testing, which
    requires that much. The crate itself should still support Rust 1.34 for now,
    but we cannot test that it continues doing so...

Fixed

  • Removed a possibility of data race that was not observed on current hardware,
    but could be triggered by future hardware or compiler evolutions. See
    #14 .

5.0.5 - 2020-07-05

16 Jan 13:18
92e64c5
Compare
Choose a tag to compare

Changed

  • Use only cache-padded instead of the full crossbeam-utils crate
  • Clean up CI config and cache Rust toolchain there

v5.0.4 - 2020-02-10

10 Feb 19:19
Compare
Choose a tag to compare

Added

  • Add a changelog to the repository.

Changed

  • Deduplicate CI configuration some more.

Fixed

  • Drop now-unnecessary manual rustfmt configuration.
  • Avoid false sharing of back-buffer information.

v5.0.3 - 2020-02-07

10 Feb 14:57
Compare
Choose a tag to compare

Changed

  • Clean up and deduplicate GitHub Actions configuration.
  • Tune down concurrent test speed to reduce CI false positives.

v5.0.2 - 2020-01-29

10 Feb 14:56
Compare
Choose a tag to compare

Changed

  • Move continuous integration to GitHub Actions.