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.

Sign up for GitHub

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

Jump to bottom

Document execution order #888

Merged
merged 7 commits into from
Jan 14, 2021
Merged

Document execution order #888

merged 7 commits into from
Jan 14, 2021

Commits on Jan 14, 2021

  1. Document evaluation order

    @Havvy
    Havvy committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    ff28b35 View commit details
    Browse the repository at this point in the history

  2. More precise terminology on evaluation order 

    I've italicized "operand" showing that it is a definition. I didn't
actually remember that being added to the reference, so I basically
tried to redefine it in the previous commit. I don't like the term, but
since it's already there, I'll just use it.

I also put in a note saying that operator precedence determines the
operands of an expression. That section could probably be written in a
style that better expresses that perspective, but I'm trying to keep
this change minimal.

I also stated that the evaluation of operands is done prior to applying
the effect. This goes in line with the beginning of the chapter with
what the meaning of an expression.

Note also that this only describes the default. Expressions that deviate
from the default already should describe their evaluation order.
    @Havvy
    Havvy committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    9379f41 View commit details
    Browse the repository at this point in the history

  3. Change sub-expression to operand in a few places

    @Havvy
    Havvy committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    02315d3 View commit details
    Browse the repository at this point in the history

  4. Explicitly list which exprs for shared eval order PR

    @Havvy
    Havvy committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    8458c78 View commit details
    Browse the repository at this point in the history

  5. Assignment expressions are *NOT* LTR evaluated. 

    This commit does not try to define their evaluation order, they just
removed them from the list of shared LTR evaluated expressions.
    @Havvy
    Havvy committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    9360ab9 View commit details
    Browse the repository at this point in the history

  6. Referencify Assignment Operator 

    I'm being wish-washy with expression/operand in the syntax section. I'm
not quite sure if we should call them `place operands` everywhere.
    @Havvy
    Havvy committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    301182e View commit details
    Browse the repository at this point in the history

  7. Execution order: Spell out uninitialized explicitly on field as well 

    It could have been read that it was any field, not just uninitialized fields.

Co-authored-by: Josh Triplett <josh@joshtriplett.org>
    @Havvy @joshtriplett
    Havvy and joshtriplett committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    6a17a57 View commit details
    Browse the repository at this point in the history