-
Notifications
You must be signed in to change notification settings - Fork 27
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
P2897 (aligned_accessor): R5 #466
Open
mhoemmen
wants to merge
13
commits into
ORNL:master
Choose a base branch
from
mhoemmen:aligned_accessor-R5
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+8,456
−788
Conversation
This file contains 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
Update based on further discussion with David Sankel. * Rename `is_checkably_valid` to `detectably_invalid` (with inverted return value) * Ask LEWG to consider the alternative design that makes `is_sufficiently_aligned` a nonmember function in `<bit>` instead of a member function of `aligned_accessor`, while LWG review of R2 proceeds concurrently * P2389R2 was voted into the Working Draft at St. Louis, so replace use of `dextents` in examples with `dims`. * Minor formatting and non-wording fixes
Add non-wording section explaining why `aligned_accessor` has no `explicit` constructor from less to more alignment.
* Make is_sufficiently_aligned a nonmember function (in the wording) * Fix nonwording sections accordingly * Minor correction in Example in Wording * Update implementation Compiler Explorer link and source code (Appendix B)
* Improve Godbolt implementation I'm submitting P2897R4.html as P2897R4 (aligned_accessor).
* Move `is_sufficiently_aligned` from `<bit>` to `<memory>`, due to feedback from LEWG mailing list review of R4 * Give `is_sufficiently_aligned` a "*Throws*: Nothing" clause and add nonwording text explaining why
This was referenced Oct 16, 2024
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.
@crtrott @dalg24 Submitted as P2897R5.
Please merge this after PRs #465, #463, PR #461.