fix documentation for nextPermutation and nextEvenPermutation #1822
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
|
LGTM. Thanks for catching this error! |
monarchdodra
added a commit
that referenced
this pull request
Dec 29, 2013
fix documentation for nextPermutation and nextEvenPermutation
|
And merged. TY. Off topic: Did you file a report about dealing with empty ranges when doing permutations? |
|
Thank you!
No - sorry, it was a problem on my side, Phobos is fine in that regard. |
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.
The three examples in the documentation are wrong:
"while (nextPermutation(a)) { }"
should in fact be
"do { } while (nextPermutation(a));"
or we miss the very first permutation. This is true for nextEvenPermutation, too.