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

[thread] “single total order” and “total order” #4537

Open
jfbastien opened this issue Mar 3, 2021 · 1 comment
Open

[thread] “single total order” and “total order” #4537

jfbastien opened this issue Mar 3, 2021 · 1 comment

Comments

@jfbastien
Copy link
Contributor

I just noticed that “single total order” and “total order” aren’t special terms in the standard’s latex… it probably needs to be from an SG1 perspective! And it seems to be used kinda loosely… and using it correctly is important!

Mutex uses “single total order” and call_once uses “total order”, it seems on purpose, but other uses I’m not sure! There aren’t that many…

This seems like an easy editorial fix (which I can send a PR for), but was wondering if it's better to go through an SG1 paper to do this from the editorial team's perspective (hence this issue).

@jensmaurer
Copy link
Member

We should be careful: sometimes, there is a global total order (e.g. memory_order_seq_cst), sometimes, there is a separate total order per object. call_once is in the latter camp, and I believe mutexes are, too.

I believe this is editorial if the phrasing in context is clear whether it refers to a global total order or a per-object total order. It would be good if Olivier Giroux could review any changes in this area.

@jensmaurer jensmaurer changed the title “single total order” and “total order” [thread] “single total order” and “total order” Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants