Changed dyn_var specialization for pointer types to return the appropriate type #65
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
…y return dyn_var of appropriate types
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.
Previously all dyn_var returned a plain old builder for the *, [] operators. But this makes accessing members from custom types difficulty.
We have now changed the specialization for all pointer types T* to return a dyn_var with the expression inside for * and []. Further more we add an implementation of -> for these types similar to how it was implemented in sample38
sample38 has been updated to not require a separate specialization for dyn_var<foo_t*> anymore. sample46 also has been updated to test the new feature.