Issue 2527: [fund.ts.v2] ALLOCATOR_OF for function::operator= has incorrect default

Title: [fund.ts.v2] ALLOCATOR_OF for function::operator= has incorrect default
Status: open
Section: [func.wrap.func.con]
Submitter: Tim Song

Created on 2015-08-04.00:00:00 last changed 82 months ago

Messages

msg8649 (view)

Date: 2016-11-20.18:55:07

Proposed resolution:

This wording is relative to N4529.

Edit [func.wrap.func.con]/p2 as indicated:

-2- In the following descriptions, let ALLOCATOR_OF(f) be the allocator specified in the construction of function f, or ~~allocator<char>()~~the value of experimental::pmr::get_default_resource() at the time of the construction of f if no allocator was specified.

msg7586 (view)

Date: 2016-11-15.00:00:00

[ 2016-11-08, Issaquah ]

Adopted during NB comment resolution

msg7504 (view)

Date: 2015-10-26.00:00:00

[ 2015-10-26 ]

Daniel adjusts wording to lib. fund. v2.

msg7503 (view)

Date: 2015-10-26.20:17:22

Addresses: fund.ts.v2

According to the table in [memory.type.erased.allocator], if no allocator argument is specified at the time of construction, the memory resource pointer used is the value of experimental::pmr::get_default_resource() at the time of construction.

Yet in [func.wrap.func.con], ALLOCATOR_OF is specified to return allocator<char>() if no allocator was specified at the time of construction, which seems incorrect, especially as the user can change the default memory resource pointer to something other than new_delete_resource().

History
Date	User	Action	Args
2017-07-30 20:10:41	admin	set	status: wp -> open
2016-11-20 18:55:07	admin	set	messages: + msg8649
2016-11-20 18:55:07	admin	set	status: new -> wp
2015-10-26 20:17:22	admin	set	messages: + msg7586
2015-08-22 13:28:04	admin	set	messages: + msg7504
2015-08-04 00:00:00	admin	create