Skip to content
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

Fix has_trivial_destructor_after_move #122

Conversation

@kariya-mitsuru
Copy link
Contributor

commented May 30, 2019

Most template type parameters 'Allocator' were modified their default type to void since 1.70.0.
These modifications cause has_trivial_destructor_after_move to compile error or yield wrong result.
So, fix them by changing specializations of has_trivial_destructor_after_move.

@kariya-mitsuru kariya-mitsuru force-pushed the kariya-mitsuru:fix-has_trivial_destructor_after_move branch from e11c0c5 to 75a23f6 May 30, 2019

Fix has_trivial_destructor_after_move
Most template type parameters 'Allocator' were modified their default type to void since 1.70.0.
These modifications cause has_trivial_destructor_after_move to compile error or yield wrong result.
So, fix them by changing specializations of has_trivial_destructor_after_move.

@kariya-mitsuru kariya-mitsuru force-pushed the kariya-mitsuru:fix-has_trivial_destructor_after_move branch from 75a23f6 to f25c767 Jun 1, 2019

@igaztanaga igaztanaga merged commit f25c767 into boostorg:develop Jun 8, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
igaztanaga added a commit that referenced this pull request Jun 8, 2019
@igaztanaga

This comment has been minimized.

Copy link
Member

commented Jun 8, 2019

Many thanks for the patch!

@kariya-mitsuru kariya-mitsuru deleted the kariya-mitsuru:fix-has_trivial_destructor_after_move branch Jun 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.