-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Document memory model of Per-field atomics #46739
Comments
I don't think this is release blocking. |
I think this got tagged with 1.9 as a kind of "forget me not", precisely because this is a core language feature that users should be able to rely on, with documentation supporting it. I fear that this issue will, like so many others tagged with |
Who is the right person to document this? Presumably @vtjnash (who I've already assigned). |
Probably, yeah, since he's the original author of the manifesto & main implementer of this? I'd offer to write it up, but I have no clue how this is implemented, what considerations were used in the implementation, what changed from manifesto to implementation etc.. Though educational, reverse engineering would probably take considerably longer and some important part would probably be missed 🤷 |
This has come up on discourse: https://discourse.julialang.org/t/calling-max-atomically-on-a-compound-type/94028?u=sukera |
As the docs say, this will be published "later":
Per-field atomics
Additionally, the linked manifesto has a number of TODOs that may or may not have been decided by now (I hope they are - some of them seem to be concerned with how this will be/is implemented..). 1.7 will have been released for 1 year in just about 3 months as of opening of this issue, so getting that done would probably be good.
The text was updated successfully, but these errors were encountered: