-
Notifications
You must be signed in to change notification settings - Fork 329
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
Resolve TODO in aligned_allocator #2298
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
df933ce
to
fa07d18
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for adding this :)
Will this be merged? |
Thanks for following up. I see that our internal CI had failed and blocked the merge. Investigating.. |
Mind if we change the check to:
? We have internal users that trip over the standard layout and trivial requirements. |
Sure. Thanks for checking! |
fa07d18
to
170daad
Compare
And updated corresponding test. AllocateAligned was designed to take trivial types only.
a466de5
to
d3b1abe
Compare
-- fa07d18 by scuzqy <[email protected]>: Resolve TODO in aligned_allocator And updated corresponding test. AllocateAligned was designed to take POD types only. COPYBARA_INTEGRATE_REVIEW=#2298 from scuzqy:AlignedAllocatorPOD fa07d18 PiperOrigin-RevId: 717822922
Merged with the proposed modification. Thanks again! |
And updated corresponding test.
AllocateAligned was designed to take POD types only.
I also removed
TestAllocateAlignedObjectWithoutDestructor
because objects with constructor/destructor are obviously illegal input.btw, restriction here can be one
is_trivial
, perhaps?