Boost v1.78.0

1. standalone-json

   1 2 10 0.0 C++

   A fork of Boost.JSON which does not require Boost

   

   The standalone Boost.JSON will be maintained in its own repo here.

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. container_hash

   2 3 34 5.7 C++

   Generic hash function for STL style unordered containers

   

   There is a list of supported combination at the very end of release notes, and C++17 on GCC11 is in there. So it should work. However, in github repo of boost.container_hash, there is already a bug report very similar to yours: https://github.com/boostorg/container_hash/issues/18 It may help if could add a reproducer example code to that bug report.

4. spirit

   3 3 406 5.5 C++

   Boost.org spirit module

   

   Sadly, this still includes the to me [rather critical bug in Boost Spirit](https://github.com/boostorg/spirit/issues/688). I was hoping that a patch would come through before release.

5. assert

   4 1 32 5.8 C++

   Boost.Assert (by boostorg)

   

   Before the Boost release archives are made, all the header files from the individual libraries (e.g. libs/assert/include/boost) are copied to a top-level boost/ directory, and then deleted. So in a Boost release archive, all library headers are in the same place, and it's no longer possible to know which header came from what library.

6. asio

   5 4 1,317 9.1 C++

   Boost.org asio module (by boostorg)

   

   On mobile so have trouble finding relevant docs, but this commit seems to contain bulk of the io_uring support: https://github.com/boostorg/asio/commit/292dcdcb94d1e5cd47b3275c1e8ad93dd19dc912

7. Boost.Asio

   6 20 5,184 9.1 C++

   Asio C++ Library

   

   As the commit (https://github.com/chriskohlhoff/asio/commit/36440a92eb83da34b7516af2632b119f83b66a35) explains, you can have io_uring to support the new I/O objects (i.e. files), but still using the epoll reactor for the other I/O objects. And that seem to be the only reason why the eventfd is there: you are still using epoll, but with io_uring through the eventfd to support things epoll doesn't support.

Suggest a related project