This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.

2184. Muddled allocator requirements for match_results assignments

Section: 31.10.1 [re.results.const], 31.10.6 [re.results.all] Status: New Submitter: Pete Becker Opened: 2012-08-29 Last modified: 2017-02-03

Priority: 3

View other active issues in [re.results.const].

View all other issues in [re.results.const].

View all issues with New status.


The effects of the two assignment operators are specified in Table 141. Table 141 makes no mention of allocators, so, presumably, they don't touch the target object's allocator. That's okay, but it leaves the question: match_results::get_allocator() is supposed to return "A copy of the Allocator that was passed to the object's constructor or, if that allocator has been replaced, a copy of the most recent replacement"; if assignment doesn't replace the allocator, how can the allocator be replaced?

Proposed resolution: