Section: 17.6.3.5 [new.delete.dataraces] Status: Resolved Submitter: DIN Opened: 2010-08-25 Last modified: 2016-01-28
Priority: Not Prioritized
View all other issues in [new.delete.dataraces].
View all issues with Resolved status.
Discussion:
Addresses DE-14
It is unclear how a user replacement function can
simultaneously satisfy the race-free conditions imposed in
this clause and query the new-handler in case of a failed
allocation with the only available, mutating interface
std::set_new_handler
.
[ Resolution proposed by ballot comment: ]
Offer a non-mutating interface to query the current new-handler.
[ 2010-10-24 Daniel adds: ]
Accepting n3122 would solve this issue. This issue is related to 1365.
[ 2010-Batavia: ]
Resolved by adopting n3189.
Proposed resolution:
Resolved in Batavia by accepting n3189.