Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

P2069 Stackable, thread local, signal guards #796

Open
wg21bot opened this issue Jan 18, 2020 · 3 comments
Open

P2069 Stackable, thread local, signal guards #796

wg21bot opened this issue Jan 18, 2020 · 3 comments

Comments

@wg21bot
Copy link
Collaborator

@wg21bot wg21bot commented Jan 18, 2020

P2069R0 Stackable, thread local, signal guards (Niall Douglas)

@wg21bot wg21bot added this to the 2020-02 milestone Jan 18, 2020
@ogiroux ogiroux added this to Wednesday in SG1 Prague Feb 6, 2020
@theres-waldo theres-waldo added this to Thursday AM in EWG-I Prague Feb 7, 2020
@brycelelbach brycelelbach removed the SG12 label Feb 8, 2020
@brycelelbach

This comment has been minimized.

Copy link
Collaborator

@brycelelbach brycelelbach commented Feb 8, 2020

Let's have SG1 and EWGI decide if they want this before we design a library API for it.

@ogiroux ogiroux moved this from Wednesday to Monday in SG1 Prague Feb 10, 2020
@erichkeane

This comment has been minimized.

Copy link
Collaborator

@erichkeane erichkeane commented Feb 13, 2020

EWGI In Prague

Given the time constraints of the committee, should we spend additional committee effort on P2069?

SF F N A SA
2 5 3 0 0

We have provided as much feedback to the author of P2069 as we intend to, so we suggest SG18(LEWGI)
review this and consider the library wording.

SF F N A SA
3 6 1 0 0
@erichkeane erichkeane removed the EWGI label Feb 13, 2020
@ogiroux

This comment has been minimized.

Copy link
Collaborator

@ogiroux ogiroux commented Feb 14, 2020

SG1 in Prague

We want (the author, and us, to spend time on) a thread safe (as far as install/uninstall)
scoped signal handler facility (i.e. the signal handler can return or call abort()).
SF F N A SA
0 8 6 1 0

We want (the author, and us, to spend time on) a signal handler facility that can cleanup
(i.e. can also not return to the protected section, but go elsewhere) (implies having
a solution to the half-updated object problem).
SF F N A SA
1 5 7 1 0

This paper needs revision to address the memory semantics of cleanup (probably comprising an even more aggressive set of prohibitions inside the guarded region, and a less-disruptive language semantic change, ideally none).

@jensmaurer jensmaurer removed this from the 2020-02 milestone Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
EWG-I Prague
Thursday AM
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.