add rfl::NamedTuple::apply() for convenient compile-time iteration #59
Conversation
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
clang on linux doesn't believe field.name() can be constexpr, so fall back to Field::name() when constexpr is required.
|
I think the compile-time name is a great idea! |
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.
Adds
rfl::NamedTuple::apply()as proposed in #58.I made one small design deviation from @liuzicheng1987's proposal which was to implement
rfl::Field::name()by way of itsrfl::internal::StringLiteralname, rather than viarfl::Literal, so that it can be a compile-time constant. I think that's important, e.g. the simple test I added wouldn't be possible without it.