Restrict atomic_ref types in accordance with the spec #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We can now add pointer-to-object-type to concept |
PeterTh
force-pushed
the
restrict-atomic-ref-types
branch
from
5736cf4 to
b05439e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I ran into this while developing some code with SimSYCL and then executing it on other platforms.
SimSYCL (helpfully, and, in my opinion, unproblematically) allows
atomic_ref<bool>, but the spec does not.It's easier to fix SimSYCL for now than the spec.
While implementing this we also found that it's currently very strange for the spec to list a limited set of types -- specifically not including any pointers -- but also a specialization for pointers. Some clarification seems needed there.