Another attempt to implement is_same_ptr() trait #9425
Merged
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
Nekotekina
force-pushed
the
atomic
branch
2 times, most recently
from
5b6934f
to
6056bdd
Compare
Implemented as constexpr function.
Can reduce compile time/overhead.
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.
It's necessary to exploit the fact that the absolutely majority of actual inheritance is linear, in a sense, that a casting between base and derived class is a no-op with the same numeric pointer value.
It's exploited by custom shared_ptr<> implementation which always contains its control block at the negative offset, and has only one pointer inside (unlike STL shared_pointer which is double sized).