Issue 2525: [fund.ts.v2] get_memory_resource should be const and noexcept

Title: [fund.ts.v2] get_memory_resource should be const and noexcept
Status: open
Section: [func.wrap.func][futures.promise][futures.task]
Submitter: Tim Song

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

Messages

msg8648 (view)

Date: 2016-11-20.18:55:07

Proposed resolution:

This wording is relative to N4529.

Edit each of the synposes in [func.wrap.func], [futures.promise], and [futures.task] as indicated:
```
pmr::memory_resource* get_memory_resource() const noexcept;
```

msg7584 (view)

Date: 2016-11-15.00:00:00

[ 2016-11-08, Issaquah ]

Adopted during NB comment resolution

msg7500 (view)

Date: 2015-10-26.00:00:00

[ 2015-10-26 ]

Daniel adjusts wording to lib. fund. v2.

msg7499 (view)

Date: 2015-10-26.20:17:22

Addresses: fund.ts.v2

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.

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: + msg8648
2016-11-20 18:55:07	admin	set	status: new -> wp
2015-10-26 20:17:22	admin	set	messages: + msg7584
2015-08-21 17:02:18	admin	set	messages: + msg7500
2015-08-04 00:00:00	admin	create