aboutsummaryrefslogtreecommitdiff
path: root/base32
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-14 16:27:21 -0800
committerDaniel Mueller <deso@posteo.net>2019-01-14 16:27:21 -0800
commit8e0badc9988775b1b0340db5b2cb975c3ecf407d (patch)
treecc8cbbf41d09ffd2d76f5dc5c0e84727e765120c /base32
parent4cf1b0c003a8bd0214e548a77bf0336148235931 (diff)
downloadnitrocli-8e0badc9988775b1b0340db5b2cb975c3ecf407d.tar.gz
nitrocli-8e0badc9988775b1b0340db5b2cb975c3ecf407d.tar.bz2
Auto-generate execute methods for generated command enums
Not too long ago we added a macro to auto generate the command enums and the required trait implementations from a concise declarative representation. This change extends this mechanism to the execute method implementation that some of those enums provide. When a tuple is specified as the "destination", e.g., here: > Enum! {ConfigCommand, [ > Get => ("get", config_get), > Set => ("set", config_set) > ]} the second component of this tuple will be interpreted as the function to invoke when this variant used in the newly generated execute method.
Diffstat (limited to 'base32')
0 files changed, 0 insertions, 0 deletions