Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that always() has a side effect #8411

Merged
merged 2 commits into from
Jul 28, 2021
Merged

Commits on Jul 21, 2021

  1. Clarify that always() has a side effect

    One straight-forward interpretation of the previous wording was that the function simply always returns `true`, with no other side effects. A reasonable conclusion would then be that, in an `if` expression, `&& always()` is redundant, and can be omitted. However, this in incorrect, as the function does have the side effect of forcing the step to be executed in addition to returning `true`.
    CyberShadow committed Jul 21, 2021
    Configuration menu
    Copy the full SHA
    05828e9 View commit details
    Browse the repository at this point in the history

Commits on Jul 28, 2021

  1. Configuration menu
    Copy the full SHA
    b6bc953 View commit details
    Browse the repository at this point in the history