-
Notifications
You must be signed in to change notification settings - Fork 128
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 Hash is duplicated in libraries list #759
Comments
Duplicate first appeared in https://www.boost.org/doc/libs/1_78_0/ |
Inside the release archive duplicate is in libs/libraries.htm file. Is it managed manually? I thought meta folder is intended to automate it and prevent such easily avoidable mistakes... $:~/Downloads/boost_1_82_0$ grep 'Container Hash' -r .
./libs/container_hash/meta/libraries.json: "name": "Container Hash",
./libs/libraries.htm: <li><a href="container_hash/index.html">Container Hash</a> - An STL-compatible hash function object that can be extended to hash user defined types, from Daniel James</li>
./libs/libraries.htm: <li><a href="container_hash/index.html">Container Hash</a> - An STL-compatible hash function object that can be extended to hash user defined types, from Daniel James</li> |
This library firstly appreared in https://www.boost.org/doc/libs/1_67_0/ |
The problem, I believe, is that it used to be a sublibrary of Functional, and then was moved into its own library. |
Try to find "Container Hash" library here https://www.boost.org/doc/libs/1_82_0/
It is listed twice in any category and any sorting option.
At first I thought that it is some kind of naming conflict, where several libraries are named "Container Hash", authored by Daniel James, added since 1.33.0, links to the same documentation page...
But no, it is obviously duplicated in the library list somehow.
I tried to find if any other library copied meta/libraries.json from Container Hash, but didn't find any. At least in master version of boost repository here on github. Maybe it was already found and fixed.
The text was updated successfully, but these errors were encountered: