Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for corresponding (0.22 sec)

  1. doc/go_mem.html

    <p>
    Channel communication is the main method of synchronization
    between goroutines.  Each send on a particular channel
    is matched to a corresponding receive from that channel,
    usually in a different goroutine.
    </p>
    
    <p class="rule">
    A send on a channel is synchronized before the completion of the
    corresponding receive from that channel.
    </p>
    
    <p>
    This program:
    </p>
    
    <pre>
    var c = make(chan int, 10)
    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)
  2. doc/go1.17_spec.html

    	<li>
    	Struct values are comparable if all their fields are comparable.
    	Two struct values are equal if their corresponding
    	non-<a href="#Blank_identifier">blank</a> fields are equal.
    	</li>
    
    	<li>
    	Array values are comparable if values of the array element type are comparable.
    	Two array values are equal if their corresponding elements are equal.
    	</li>
    </ul>
    
    <p>
    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)
  3. doc/go_spec.html

    The type parameter names do not need to match their corresponding parameter names in the
    receiver base type definition, and all non-blank parameter names must be unique in the
    receiver parameter section and the method signature.
    The receiver type parameter constraints are implied by the receiver base type definition:
    corresponding type parameters have corresponding constraints.
    </p>
    
    <pre>
    type Pair[A, B any] struct {
    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)
Back to top