Matthew Stoltenberg

Ok, I'm probably missing something (or have some odd interaction with the normal syntax highlighter). I set this in my vimrc: ``` let g:rainbow_conf = {'guis': ['bold']} let g:rainbow_active =...

Just wanted to add my use case: I need to limit both the cpus and mems a process can utilize to eliminate any accidental cross-NUMA memory bandwidth using the --cpuset-cpus...

Just to add that I have several container builds, copying in my own app and corresponding glibc, that used the :latest container not realizing that it was going to change...

FWIW: as of boost 1.84, boost::ratio is a type alias of std::ratio. So Point 1 above should be done...

I'm pretty sure the noexcept specifier should match the one from std::vector. Something like: ``` noexcept(std::allocator_traits::propagate_on_container_move_assignment::value || std::allocator_traits::is_always_equal::value) ```

@memsharded (sorry to resurrect a months old issue) if multiple binary packages are really to be avoided... Could `conan upload` default to not upload binary packages that match something already...

I could open a PR with a patch that looks something like this below. I've only tested it so far with gcc14 on Linux x86_64, but it makes TSAN happy...