Repository navigation
Document short-circuit evaluation of and/or on the Boolean page - #2265
Merged
Merged
Conversation
Contributor
|
Thanks |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #2072
The Language Reference Guide's operators page already says
andandorshort-circuit, but the Boolean type page doesn't mention it, which is where the issue went looking. This adds a short "Short-circuit evaluation" section tobool.mdexplaining when the right-hand side is skipped, with an example using a command that prints when it is called, and one showing a guard (($text != "") and (...)).I ran the examples with nu 0.116.2 and the output matches what the page shows.
prettier --checkpasses on the file.