- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for called (0.14 sec)
-
doc/go_mem.html
and the matching call to <code>l.RUnlock</code> is synchronized before the return from call <i>n</i>+1 to <code>l.Lock</code>. </p> <p class="rule"> A successful call to <code>l.TryLock</code> (or <code>l.TryRLock</code>) is equivalent to a call to <code>l.Lock</code> (or <code>l.RLock</code>). An unsuccessful call has no synchronizing effect at all. As far as the memory model is concerned,
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0) -
doc/go1.17_spec.html
the function call. </p> <p> The final case, a value-receiver function for a pointer-receiver method, is illegal because pointer-receiver methods are not in the method set of the value type. </p> <p> Function values derived from methods are called with function call syntax; the receiver is provided as the first argument to the call.
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
doc/go_spec.html
execution terminates by returning to its caller. </p> <p> The return value of <code>recover</code> is <code>nil</code> when the goroutine is not panicking or <code>recover</code> was not called directly by a deferred function. Conversely, if a goroutine is panicking and <code>recover</code> was called directly by a deferred function,
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu May 02 22:43:51 GMT 2024 - 279.6K bytes - Viewed (0)