- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for evaluation (0.25 sec)
-
doc/go1.17_spec.html
However, the order of those events compared to the evaluation and indexing of <code>x</code> and the evaluation of <code>y</code> is not specified. </p> <pre> a := 1 f := func() int { a++; return a } x := []int{a, f()} // x may be [1, 2] or [2, 2]: evaluation order between a and f() is not specified m := map[int]int{a: 1, a: 2} // m may be {2: 1} or {2: 2}: evaluation order between the two map assignments is not specified
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
src/cmd/asm/internal/asm/expr_test.go
// Junk at EOF. {"3 x", 3, false}, // Big number {"4611686018427387904", 4611686018427387904, true}, } func TestExpr(t *testing.T) { p := NewParser(nil, nil, nil) // Expression evaluation uses none of these fields of the parser. for i, test := range exprTests { p.start(lex.Tokenize(test.input)) result := int64(p.expr()) if result != test.output {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Aug 29 07:48:38 GMT 2023 - 3.2K bytes - Viewed (0) -
doc/go_spec.html
precision, and vice versa. </p> <h3 id="Order_of_evaluation">Order of evaluation</h3> <p> At package level, <a href="#Package_initialization">initialization dependencies</a> determine the evaluation order of individual initialization expressions in <a href="#Variable_declarations">variable declarations</a>. Otherwise, when evaluating the <a href="#Operands">operands</a> of an expression, assignment, or
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Apr 26 00:39:16 GMT 2024 - 279.6K bytes - Viewed (0) -
src/cmd/asm/internal/asm/parse.go
// compared to the old yacc/C implementations. Neither has // much practical consequence because the expressions we // see in assembly code are simple, but for the record: // // 1) Evaluation uses uint64; the old one used int64. // 2) Precedence uses Go rules not C rules. // expr = term | term ('+' | '-' | '|' | '^') term. func (p *Parser) expr() uint64 { value := p.term() for {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Feb 21 14:34:57 GMT 2024 - 36.9K bytes - Viewed (0) -
doc/asm.html
</pre> <h3 id="constants">Constants</h3> <p> Although the assembler takes its guidance from the Plan 9 assemblers, it is a distinct program, so there are some differences. One is in constant evaluation. Constant expressions in the assembler are parsed using Go's operator precedence, not the C-like precedence of the original. Thus <code>3&1<<2</code> is 4, not 0—it parses as <code>(3&1)<<2</code>
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/11-language-change.yml
description: Changes to the language labels: ["Proposal", "v2", "LanguageChange"] title: "proposal: Go 2: proposal title" body: - type: markdown attributes: value: | ## Our process for evaluating language changes can be found [here](https://go.googlesource.com/proposal/+/refs/heads/master#language-changes) - type: dropdown id: author-go-experience attributes: label: "Go Programming Experience"
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Nov 22 20:49:24 GMT 2023 - 4.7K bytes - Viewed (0) -
doc/go_mem.html
defined as the partial order requirements set out by the <a href="/ref/spec">Go language specification</a> for Go's control flow constructs as well as the <a href="/ref/spec#Order_of_evaluation">order of evaluation for expressions</a>. </p> <p> A Go <i>program execution</i> is modeled as a set of goroutine executions,
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0)