This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of TS status.
Section: 4.2 [fund.ts.v2::func.wrap.func], 11.2 [fund.ts.v2::futures.promise], 11.3 [fund.ts.v2::futures.task] Status: TS Submitter: Tim Song Opened: 2015-08-04 Last modified: 2017-07-30
View all other issues in [fund.ts.v2::func.wrap.func].
View all issues with TS status.
There doesn't seem to be any reason why this member function cannot be called on a const object, or why it would ever throw. I discussed this with Pablo Halpern, the author of N3916, and he agrees that this appears to have been an oversight.
Daniel adjusts wording to lib. fund. v2.
Adopted during NB comment resolution
This wording is relative to N4529.
Edit each of the synposes in 4.2 [fund.ts.v2::func.wrap.func], 11.2 [fund.ts.v2::futures.promise], and 11.3 [fund.ts.v2::futures.task] as indicated:
pmr::memory_resource* get_memory_resource() ;