Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for shend (0.16 sec)

  1. doc/go1.17_spec.html

    begins. Communication blocks until the send can proceed.
    A send on an unbuffered channel can proceed if a receiver is ready.
    A send on a buffered channel can proceed if there is room in the buffer.
    A send on a closed channel proceeds by causing a <a href="#Run_time_panics">run-time panic</a>.
    A send on a <code>nil</code> channel blocks forever.
    </p>
    
    <pre>
    ch &lt;- 3  // send value 3 to channel ch
    </pre>
    
    
    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)
  2. doc/go_mem.html

    <h3 id="chan">Channel communication</h3>
    
    <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>
    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)
  3. doc/go_spec.html

    begins. Communication blocks until the send can proceed.
    A send on an unbuffered channel can proceed if a receiver is ready.
    A send on a buffered channel can proceed if there is room in the buffer.
    A send on a closed channel proceeds by causing a <a href="#Run_time_panics">run-time panic</a>.
    A send on a <code>nil</code> channel blocks forever.
    </p>
    
    <pre>
    ch &lt;- 3  // send value 3 to channel ch
    </pre>
    
    
    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