New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[container.opt.reqmts] Index 3-way compare for containers #6220
[container.opt.reqmts] Index 3-way compare for containers #6220
Conversation
All of the standard containers are 3-way comparable, but the specification is provided under optional container requirements so does not show up in the index. Adding these links shows just how poorly indexed the members of the 'flat_*' container adapters are, but that is properly the business on a separate PR.
Co-authored-by: Johel Ernesto Guerrero Peña <johelegp@gmail.com>
This form seems a closer match to how the other container requirements operations are indexed, where we get just one generic entry in the index for "optional container requirements" and a specific entry for the operator on each listed container.
I think we now have two options: the original version of the PR, or the current state where I use a local macro to index all operations with a grouped text-name, while retaining the correct indexing in each container. @tkoeppe @jensmaurer @jwakely could you express a preference? |
Co-authored-by: Johel Ernesto Guerrero Peña <johelegp@gmail.com>
The current state with |
@jwakely Any thoughts? |
Co-authored-by: Jonathan Wakely <github@kayari.org>
All of the standard containers are 3-way comparable, but the specification is provided under optional container requirements so does not show up in the index.
Adding these links shows just how poorly indexed the members of the 'flat_*' container adapters are, but that is properly the business on a separate PR.