Fix references to container requirements tables. #1905
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LWG issue 704 ("MoveAssignable requirement for container value type overly strict") added a reference from [associative.reqmts] to what was at the time table 93 ("Allocator-aware container requirements").
That table is now table 86, but the cross reference is now (incorrectly) to table 83 ("Container requirements"). It should still refer to the Allocator-ware container requirements table. This patch changes it to do so, matching what the committee voted in (many years ago).