Skip to content

spec: evaluation order of statements unspecified #10954

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
Open
griesemer opened this issue May 26, 2015 · 5 comments
Open

spec: evaluation order of statements unspecified #10954

griesemer opened this issue May 26, 2015 · 5 comments
Labels
Documentation Issues describing a change to documentation. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unplanned

Comments

@griesemer
Copy link
Contributor

The order is obvious to everybody but there should probably be a sentence somewhere.
@griesemer griesemer added the Documentation Issues describing a change to documentation. label May 26, 2015
@griesemer griesemer self-assigned this May 26, 2015
@griesemer griesemer added this to the Unplanned milestone May 26, 2015
@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 13, 2024
@linsite
Copy link
Contributor

linsite commented Feb 26, 2025

is this already covered by https://tip.golang.org/ref/spec#Order_of_evaluation?

@griesemer
Copy link
Contributor Author

That section specifies the evaluation order within a single expression.

@linsite
Copy link
Contributor

linsite commented Mar 3, 2025 •
edited
Loading

Can I give it a try? I think it can be specified at different levels.
The top down orders are:

  1. module level
  2. package level
  3. function level
  4. expression level( existed)

@griesemer
Copy link
Contributor Author

@linsite Thanks, but a) this is not urgent, and b) we (Go team) prefer to take care of this. Getting spec prose right is notoriously difficult.

@linsite
Copy link
Contributor

linsite commented Mar 4, 2025

Yes, I can understand that, looking forward to the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Documentation Issues describing a change to documentation. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
3 participants
@griesemer @seankhliao @linsite