Improve enumerate macro #8819
Merged
Improve enumerate macro #8819
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
Previously line breaks were so weird that the code blocks were not created.
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.
After discussion in irc about issue #8818 (https://irclogs.nim-lang.org/30-08-2018.html#15:54:55), the experimental
enumeratemacro was proposed as a workaround.This PR wraps the example macro in the manual in a block to create a new scope to avoid polluting the calling scope with a bunch of (to be reused) variable names.
I left the test case untouched and also fixed the line breaks for the case statement macro in the manual below, which previously (for me locally anyways) wouldn't produce a code block.