- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 10 for evaluator (0.34 sec)
-
doc/go_spec.html
The expression <code>x</code> is evaluated and saved during the evaluation of the method value; the saved copy is then used as the receiver in any calls, which may be executed later. </p> <pre> type S struct { *T } type T int func (t T) M() { print(t) } t := new(T) s := S{T: t} f := t.M // receiver *t is evaluated and stored in f
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) -
src/cmd/asm/internal/asm/asm.go
return false } if !offsetOk && addr.Offset != 0 { p.errorf("%s symbol %q must not be offset from SB", pseudo, symbolName(addr)) return false } return true } // evalInteger evaluates an integer constant for a pseudo-op. func (p *Parser) evalInteger(pseudo string, operands []lex.Token) int64 { addr := p.address(operands) return p.getConstantPseudo(pseudo, &addr) }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Feb 21 14:34:57 GMT 2024 - 25.3K bytes - Viewed (0) -
src/cmd/asm/internal/asm/expr_test.go
} 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 { t.Errorf("%d: %q evaluated to %d; expected %d", i, test.input, result, test.output) } tok := p.next()
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/godebug.md
always have [`os.ModeIrregular`](/pkg/os#ModeIrregular) set. As a result of these changes, [`filepath.EvalSymlinks`](/pkg/path/filepath#EvalSymlinks) no longer evaluates mount points, which was a source of many inconsistencies and bugs. At previous versions (`winsymlink=0`), mount points are treated as symlinks, and other reparse points with non-default [`os.ModeType`](/pkg/os#ModeType) bits
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 16 17:29:58 GMT 2024 - 13.5K bytes - Viewed (0) -
doc/asm.html
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> not <code>3&(1<<2)</code>. Also, constants are always evaluated as 64-bit unsigned integers.
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) -
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/cgo/gcc.go
// literal to evaluate the arguments at the right time. // defer func() func() { // _cgo0 := p // return func() { // _cgoCheckPointer(_cgo0, nil) // C.f(_cgo0) // } // }()() // This works because the defer statement evaluates the first // function literal in order to get the function to call.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Nov 02 16:43:23 GMT 2023 - 97K bytes - Viewed (0) -
doc/next/6-stdlib/99-minor/path/filepath/63703.md
On Windows, [EvalSymlinks] no longer evaluates mount points, which was a source of many inconsistencies and bugs. This behavior is controlled by the `winsymlink` setting. For Go 1.23, it defaults to `winsymlink=1`. Previous versions default to `winsymlink=0`. On Windows, [EvalSymlinks] no longer tries to normalize volumes to drive letters, which was not always even possible. This behavior is controlled by the `winreadlinkvolume` setting.
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Apr 12 20:57:18 GMT 2024 - 545 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)