This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD Future status.
Section: 22.10.19 [unord.hash] Status: NAD Future Submitter: Alisdair Meredith Opened: 2009-03-11 Last modified: 2020-08-21
Priority: Not Prioritized
View all other issues in [unord.hash].
View all issues with NAD Future status.
Discussion:
Addresses UK 208 [CD1]
std::hash should be implemented for much more of the standard library. In particular for pair, tuple and all the standard containers.
[2020-05-28; LEWG issue reviewing]
At the Kona 2017 LEWG issue processing session, this issue was marked as NAD. The formatting of the LWGissuesInLEWGStatus page ran 1025 into other text. A search of the page yields:
1025 20.14.15 [unord.hash] The library should provide more specializations for std::hash NAD: We don't want to do this before solving LEWG21.
Status change to Open.
[2020-08-21 Issue processing telecon: follow LEWG recommendation. Status changed: Open → NAD Future.]
Proposed resolution: