P1007R3 std::assume_aligned #2467
Conversation
|
I fixed the trailing whitespace and committed to the branch - how do I get this PR to see the new change? Note: I didn't rebase and force push since @jwakely said we should no longer do that. Never mind, github just saw the new commit and is rechecking - cool!! |
|
@burblebee, please make sure you prefix commit comments with "Fixup:" if you want them squashed by @zygoloid upon merge. (Removing training whitespace certainly qualifies.) |
|
@burblebee: You don't need to take any action. Pull requests are always for branches, not for commits. |
|
@tkoeppe, right, but I'd like Dawn to avoid the issue going forward. |
@jensmaurer Thanks for this tip! @zygoloid, all the commits made after the initial paper in branches motions-2018-11-lwg-16, motions-2018-11-lwg-17, motions-2018-11-lwg-9, and motions-2018-11-lwg-4 should have been prefixed with "Fixup:". Note that in motions-2018-11-lwg-4 you'll want to rebase in order to squash the fixes in with their corresponding issue. I can force push if you prefer. |
jensmaurer
added
the
changes requested
burblebee
removed
the
changes requested
[memory.syn] Merged the new function in with [ptr.align] and renamed the section to "Pointer alignment". [ptr.aligned] Added "a" before "type similar".
zygoloid
force-pushed
the
motions-2018-11-lwg-17
branch
from
2074145
to
2f46621
Compare
[memory.syn] Merged the new function in with [ptr.align] and
renamed the section to "Pointer alignment".
[ptr.aligned] Added "a" before "type similar".
Fixes #2423.