All tests passed 4e228c42890148ea8f6f5a08ba7c6e4e9fc15468

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed 0f6df25eb0f1f383ef3061bdf72007fd5014f759

Try using `BOOST_ASSERT` instead of `assert` in Boost.Outcome, see
what happens.

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

v2.2.8 Boost 1.84 release

v2.2.8 13th December 2023 (Boost 1.84) [release]

Enhancements:

• cmake 3.9 is now the minimum required for standalone Outcome. This fixes a long standing
  cmake issue with probing for standard library facilities. cmake 3.9 is what RHEL7 ships with,
  when RHEL7 EOLs we may raise the minimum cmake version at that point.

Bug fixes:

• There was a bug in the Outcome C++ coroutine awaitables whereby we were over eagerly resuming
  execution of coroutines which return one of our awaitables. It is surprising how many years have
  passed before this was noticed, but it is now fixed. It is believed that this has been fixed
  without affecting ABI stability, however mixing old Outcome and new Outcome in the same binary
  without recompiling all the C++ coroutine code to use new Outcome will not fix the bug.

#291

• A Result or Outcome with void value type and move-only non-value type was only usable in
  const use cases, due to the lack of provision of non-const member functions in relevant observers
  injection layers for the void specialisation. The missing non-const member functions have now
  been added.

---

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed d4d196619d5708834dd880fd62637b657e9a30ad

Fixes #293
- Some users wished that Outcome would be clean with `-Wpedantic`, this is now turned on for
the test suite.

Fixes #294
- All use of `assert()` has been replaced with `OUTCOME_ASSERT`, which can be user overridden
at compile time.

Fixes #295
- In git commit 12b14e1533848e9a0f7f3c38e41da0ee4e819770 (Aug 11 2022) status code had its
paths changed due to its headers not previously having the right path convention. It was not
realised at the time that in Boost.Outcome this resulted in
`<boost/outcome/experimental/status-code/status-code/headers.hpp>` which is not desirable.
This has now been remedied to remove the double `status-code`, which will obviously break
any Boost.Outcome code which relies on the double `status-code`. Standalone Outcome is unaffected.

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed 893c2d0fb8f00b7afe8daf4a6f2782f3d11fc1ae

upd

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed f7892ac2e8ef0a236f324a9111e75824ae55690a

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed ec53527dc5bca766d8468fec88d8cd657b5194f1

Merge pull request #290 from BurningEnlightenment/dev/require-cmake-3.9

build: Require at least CMake 3.9

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed 441e3164801151ae7671ea331a04b4a712f505e9

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed e33619767469a29c7e65edd69a700998c801ad6a

Fix Boost CI

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies:

All tests passed 1f972ef2c8365afd9dfb92f0bbb953fb06b61abe

Use the 'all-sources' tarball below, NOT the github generated one which is missing dependencies: