- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for Caller (0.17 sec)
-
doc/go_mem.html
can only have outcomes explained by some sequentially consistent interleaving of the goroutine executions. (The proof is the same as Section 7 of Boehm and Adve's paper cited above.) This property is called DRF-SC. </p> <p> The intent of the formal definition is to match the DRF-SC guarantee provided to race-free programs by other languages, including C, C++, Java, JavaScript, Rust, and Swift. </p> <p>
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0) -
doc/go1.22.html
This is equivalent to calling <code>time.Now().Sub(t)</code> before the <code>defer</code> statement, not when the deferred function is called. In nearly all cases, the correct code requires deferring the <code>time.Since</code> call. For example: </p> <pre> t := time.Now() defer log.Println(time.Since(t)) // non-deferred call to time.Since
HTML - Registered: Tue Feb 06 11:13:10 GMT 2024 - Last Modified: Wed Jan 31 20:51:56 GMT 2024 - 45.6K bytes - Viewed (0) -
doc/go1.17_spec.html
<a href="#Order_of_evaluation">the usual order</a>. After they are evaluated, the parameters of the call are passed by value to the function and the called function begins execution. The return parameters of the function are passed by value back to the caller when the function returns. </p> <p> Calling a <code>nil</code> function value causes a <a href="#Run_time_panics">run-time panic</a>. </p>
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
doc/asm.html
(It's not a subtraction, just idiosyncratic syntax.) The frame size <code>$24-8</code> states that the function has a 24-byte frame and is called with 8 bytes of argument, which live on the caller's frame. If <code>NOSPLIT</code> is not specified for the <code>TEXT</code>, the argument size must be provided.
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0) -
doc/go_spec.html
are then executed as usual. Next, any deferred functions run by <code>F</code>'s caller are run, and so on up to any deferred by the top-level function in the executing goroutine. At that point, the program is terminated and the error condition is reported, including the value of the argument to <code>panic</code>. This termination sequence is called <i>panicking</i>. </p> <pre> panic(42) panic("unreachable")
HTML - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 279.3K bytes - Viewed (0)