This repository was archived by the owner on Jan 29, 2026. It is now read-only.
Merged
Conversation
…/proxy into user/mingxwa/indirection
tian-lt
reviewed
Jun 24, 2024
tian-lt
approved these changes
Jun 24, 2024
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
Dapplies to a pointer, or the target of a pointer, is now determined byD::is_direct(required to be provided asstatic constexpr bool). In the previous design, this was determined by overload resolution, which makes the semantics ambiguous.Ralso requiresR::is_directto be provided asstatic constexpr bool.proxy, while indirect accessors are available viaproxy::operator->orproxy::operator*.PRO_DEF_MEM_DISPATCH) defaults to indirect: