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.

Sign up for GitHub

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

Jump to bottom

[thread.mutex] Mutex types defined in requirements #362

Open
K-ballo opened this issue Aug 10, 2014 · 4 comments
Open

[thread.mutex] Mutex types defined in requirements #362

K-ballo opened this issue Aug 10, 2014 · 4 comments
Labels
lwg Issue must be reviewed by LWG. not-editorial Issue is not deemed editorial; the editorial issue is kept open for tracking.

Comments

@K-ballo
Copy link
Contributor

K-ballo commented Aug 10, 2014

The mutex types are defined together with their requirements, under the "Mutex Requirements" [thread.mutex.requirements] section. This feels a bit odd.

I was expecting only the requirements to be defined under "Mutex Requirements", and the actual classes to be defined in their own sections, at the same level of requirements. See for example how the [containers] clause is specified.
@jensmaurer
Copy link
Member

We could certainly move the subclauses containing the class definitions directly under [thread.mutex]. I'm not sure it would be a net improvement.

@jensmaurer jensmaurer assigned jensmaurer and unassigned jensmaurer Nov 30, 2017
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 30, 2017
@jensmaurer jensmaurer added lwg Issue must be reviewed by LWG. not-editorial Issue is not deemed editorial; the editorial issue is kept open for tracking. and removed decision-required A decision of the editorial group (or the Project Editor) is required. labels Mar 18, 2018
@zygoloid
Copy link
Member

It seems like we have mixed together two things here: a set of requirements on mutex types, and a description of some concrete types that satisfy those requirements. We should describe the requirements abstractly, and then say that the standard library mutex types meet them, as we do with containers etc.

This is a large reorganization, and I'd like to request that LWG find someone to pursue it rather than us doing it editorially.

@jwakely jwakely self-assigned this Mar 18, 2018
@jwakely
Copy link
Member

jwakely commented Mar 18, 2018

I'll write a P-paper proposing that reorg.

@jwakely
Copy link
Member

jwakely commented Mar 20, 2018

Unassigning myself, as I don't plan to work on this now.

@jwakely jwakely removed their assignment Mar 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lwg Issue must be reviewed by LWG. not-editorial Issue is not deemed editorial; the editorial issue is kept open for tracking.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zygoloid @jwakely @K-ballo @jensmaurer