@@ -42,7 +42,7 @@ The type *channel* is conceptually the blocking queue. In Go, its implemented i
The `select` operation has been in OS kernels long before Go language. All Unix kernels implement system calls *poll* and *select*. They monitor multiple file descriptors to see if I/O is possible on any of them. This takes O(N) time. Since Linux 2.6, a new system call, *epoll*, can do the same in O(1) time. In BSD systems, there is a similar system call *kqueue*. Go's Linux implementation uses epoll.
It might be a good idea to implement Fluid's select using epoll too. In this design doc, we start from the O(N) way, so we could focus on Python binding and the syntax.
It might be a good idea to implement Fluid's select using epoll too. In this design doc, we start from the O(N) way so that we could focus on Python binding and the syntax.
### Type Channel
...
...
@@ -87,79 +87,87 @@ The point here is that we need a consistent way to compose types, like in C++ we
### Send and Recv
In Go, we first create a channel as explained in the section above and then perform read and write operations on top of the channels.
Go's CSP implementation depends on data type *channel*. There are two types of channels:
```go
ch1 := make(chan int)
ch2 := make(chan int, 100)
```
1. The unblocked channel, or buffered channel, is a blocking queue with a non-zero sized buffer. The sending to buffered channel blocks if the buffer is full, and the receive operation blocks if the buffer is empty.
1. blocked channel, or unbuffered channel, is a blocking queue with no buffer. Both sending and receiving block with unbuffered channels.
To write (or perform a `Send` operation) the value of a variable `x`, to channel `ch1` above, we perform the following:
There are four types of actions with a channel:
```go
ch1 <- x
fmt.Println("Written to the channel")
```
Now to read (or perform a `Recv` operation) the value stored in `ch2` into a variable `y`, we perform the following:
1. Create a channel
```go
y <- ch2
fmt.Println("Received from channel")
```
```go
ch := make(chan int) // this is an unbuffered channel
ch := make(chan int, 100) // this is a buffered channel of 100 ints.
```
In Fluid, we should be able to perform the above operations on the channel objects as well. As of now, we support two different kinds of channels : [Buffered Channel](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h) and [UnBuffered Channel](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h)
1. Send
Send and Receive can be performed as following on a buffered channel:
Please be aware that a closed channel is not a nil channel, which is `var ch chan int`.
There are some [axioms with channels](https://dave.cheney.net/2014/03/19/channel-axioms):
# Read all the data from the channel
for i in xrange(3):
y = ch.recv()
1. A send to a nil channel blocks forever
# Done receiving , now close the channel
ch.close()
```
1. A receive from a nil channel blocks forever
1. A send to a closed channel panics
1. A receive from a closed channel returns the residual values and then zeros.
The send and receive operations will be similar for unbuffered channel as well, except for the fact that there is no buffer in an unbuffered channel, so the operations are completely synchronized. For example:
In Fluid, we have [buffered channels](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h) and [unbuffered channels](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h)
The following program illustrates the Python syntax for accessing Fluid buffers.
```python
import threading
import fluid
buffer_size = 10
ch = fluid.make_channel(dtype=INT, buffer_size)
def send_to_channel(channel, data):
channel.send(data)
# Now write three elements to the channel
with fluid.while(steps=buffer_size):
fluid.send(ch, step)
fluid.close_channel(ch)
with fluid.while(steps=buffer_size):
fluid.print(fluid.recv(ch))
```
The following example shows that to avoid the always-blocking behavior of unbuffered channels, we need to use Fluid's goroutines.
```python
import fluid
# Create an unbuffered channel
ch = fluid.make_channel(dtype=INT)
# Writes and Reads are synchronous otherwise the calls will block.
In Go, the `select` statement lets a goroutine wait on multiple communication operations. A `select` blocks untill one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.
In Go, the `select` statement lets a goroutine wait on multiple communication operations. A `select` blocks until one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.
```go
...
...
@@ -202,9 +210,9 @@ with sel.default():
In the above code snippet, `X` and `Y` are variables. Now let us look at each of these statements one by one.
- `sel.case(ch1, 'w', X)` : This specifies that we are writing to `ch1` and we want to write the integer in variable `X` to the channel. The character `w` is used here to make the syntax familar to write syntax in Python I/O.
- `sel.case(ch1, 'w', X)` : This specifies that we are writing to `ch1` and we want to write the integer in variable `X` to the channel. The character `w` is used here to make the syntax familiar to write syntax in Python I/O.
- `sel.case(ch2, 'r', Y)` : This specifies that we would like to read the result from `ch2` into variable `Y`. The character `r` is used here to make the syntax familar to read syntax in Python I/O.
- `sel.case(ch2, 'r', Y)` : This specifies that we would like to read the result from `ch2` into variable `Y`. The character `r` is used here to make the syntax familiar to read syntax in Python I/O.
- `sel.default()` : This is equivalent to the default in Go `select`. If none of the channels are ready for read or write, then the fluid code in the default block will be executed.
<p>We also need Python wrappers for the above components.</p>
<p>The type <em>channel</em> is conceptually the blocking queue. In Go, its implemented is a <aclass="reference external"href="https://github.com/golang/go/blob/68ce117cf17b8debf5754bfd476345779b5b6616/src/runtime/chan.go#L31-L50">blocking circular queue</a>, which supports send and recv.</p>
<p>The <codeclass="docutils literal"><spanclass="pre">select</span></code> operation has been in OS kernels long before Go language. All Unix kernels implement system calls <em>poll</em> and <em>select</em>. They monitor multiple file descriptors to see if I/O is possible on any of them. This takes O(N) time. Since Linux 2.6, a new system call, <em>epoll</em>, can do the same in O(1) time. In BSD systems, there is a similar system call <em>kqueue</em>. Go’s Linux implementation uses epoll.</p>
<p>It might be a good idea to implement Fluid’s select using epoll too. In this design doc, we start from the O(N) way, so we could focus on Python binding and the syntax.</p>
<p>It might be a good idea to implement Fluid’s select using epoll too. In this design doc, we start from the O(N) way so that we could focus on Python binding and the syntax.</p>
<divclass="section"id="type-channel">
<spanid="type-channel"></span><h3>Type Channel<aclass="headerlink"href="#type-channel"title="Permalink to this headline">¶</a></h3>
<p>Fluid supports many data types:</p>
...
...
@@ -278,70 +278,76 @@
</div>
<divclass="section"id="send-and-recv">
<spanid="send-and-recv"></span><h3>Send and Recv<aclass="headerlink"href="#send-and-recv"title="Permalink to this headline">¶</a></h3>
<p>In Go, we first create a channel as explained in the section above and then perform read and write operations on top of the channels.</p>
<p>Go’s CSP implementation depends on data type <em>channel</em>. There are two types of channels:</p>
<olclass="simple">
<li>The unblocked channel, or buffered channel, is a blocking queue with a non-zero sized buffer. The sending to buffered channel blocks if the buffer is full, and the receive operation blocks if the buffer is empty.</li>
<li>blocked channel, or unbuffered channel, is a blocking queue with no buffer. Both sending and receiving block with unbuffered channels.</li>
</ol>
<p>There are four types of actions with a channel:</p>
<ol>
<li><pclass="first">Create a channel</p>
<divclass="highlight-go"><divclass="highlight"><pre><span></span><spanclass="nx">ch</span><spanclass="o">:=</span><spanclass="nb">make</span><spanclass="p">(</span><spanclass="kd">chan</span><spanclass="kt">int</span><spanclass="p">)</span><spanclass="c1">// this is an unbuffered channel</span>
<spanclass="nx">ch</span><spanclass="o">:=</span><spanclass="nb">make</span><spanclass="p">(</span><spanclass="kd">chan</span><spanclass="kt">int</span><spanclass="p">,</span><spanclass="mi">100</span><spanclass="p">)</span><spanclass="c1">// this is a buffered channel of 100 ints.</span>
</pre></div>
</div>
<p>To write (or perform a <codeclass="docutils literal"><spanclass="pre">Send</span></code> operation) the value of a variable <codeclass="docutils literal"><spanclass="pre">x</span></code>, to channel <codeclass="docutils literal"><spanclass="pre">ch1</span></code> above, we perform the following:</p>
<spanclass="nx">fmt</span><spanclass="p">.</span><spanclass="nx">Println</span><spanclass="p">(</span><spanclass="s">"Written to the channel"</span><spanclass="p">)</span>
<p>Now to read (or perform a <codeclass="docutils literal"><spanclass="pre">Recv</span></code> operation) the value stored in <codeclass="docutils literal"><spanclass="pre">ch2</span></code> into a variable <codeclass="docutils literal"><spanclass="pre">y</span></code>, we perform the following:</p>
<spanclass="nx">fmt</span><spanclass="p">.</span><spanclass="nx">Println</span><spanclass="p">(</span><spanclass="s">"Received from channel"</span><spanclass="p">)</span>
<p>In Fluid, we should be able to perform the above operations on the channel objects as well. As of now, we support two different kinds of channels : <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h">Buffered Channel</a> and <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h">UnBuffered Channel</a></p>
<p>Send and Receive can be performed as following on a buffered channel:</p>
<p>Please be aware that a closed channel is not a nil channel, which is <codeclass="docutils literal"><spanclass="pre">var</span><spanclass="pre">ch</span><spanclass="pre">chan</span><spanclass="pre">int</span></code>.</p>
</li>
</ol>
<p>There are some <aclass="reference external"href="https://dave.cheney.net/2014/03/19/channel-axioms">axioms with channels</a>:</p>
<olclass="simple">
<li>A send to a nil channel blocks forever</li>
<li>A receive from a nil channel blocks forever</li>
<li>A send to a closed channel panics</li>
<li>A receive from a closed channel returns the residual values and then zeros.</li>
</ol>
<p>In Fluid, we have <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h">buffered channels</a> and <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h">unbuffered channels</a></p>
<p>The following program illustrates the Python syntax for accessing Fluid buffers.</p>
<p>The send and receive operations will be similar for unbuffered channel as well, except for the fact that there is no buffer in an unbuffered channel, so the operations are completely synchronized. For example:</p>
<spanid="select"></span><h3>Select<aclass="headerlink"href="#select"title="Permalink to this headline">¶</a></h3>
<p>In Go, the <codeclass="docutils literal"><spanclass="pre">select</span></code> statement lets a goroutine wait on multiple communication operations. A <codeclass="docutils literal"><spanclass="pre">select</span></code> blocks untill one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.</p>
<p>In Go, the <codeclass="docutils literal"><spanclass="pre">select</span></code> statement lets a goroutine wait on multiple communication operations. A <codeclass="docutils literal"><spanclass="pre">select</span></code> blocks until one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.</p>
<p>In the above code snippet, <codeclass="docutils literal"><spanclass="pre">X</span></code> and <codeclass="docutils literal"><spanclass="pre">Y</span></code> are variables. Now let us look at each of these statements one by one.</p>
<ulclass="simple">
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch1,</span><spanclass="pre">'w',</span><spanclass="pre">X)</span></code> : This specifies that we are writing to <codeclass="docutils literal"><spanclass="pre">ch1</span></code> and we want to write the integer in variable <codeclass="docutils literal"><spanclass="pre">X</span></code> to the channel. The character <codeclass="docutils literal"><spanclass="pre">w</span></code> is used here to make the syntax familar to write syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch2,</span><spanclass="pre">'r',</span><spanclass="pre">Y)</span></code> : This specifies that we would like to read the result from <codeclass="docutils literal"><spanclass="pre">ch2</span></code> into variable <codeclass="docutils literal"><spanclass="pre">Y</span></code>. The character <codeclass="docutils literal"><spanclass="pre">r</span></code> is used here to make the syntax familar to read syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch1,</span><spanclass="pre">'w',</span><spanclass="pre">X)</span></code> : This specifies that we are writing to <codeclass="docutils literal"><spanclass="pre">ch1</span></code> and we want to write the integer in variable <codeclass="docutils literal"><spanclass="pre">X</span></code> to the channel. The character <codeclass="docutils literal"><spanclass="pre">w</span></code> is used here to make the syntax familiar to write syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch2,</span><spanclass="pre">'r',</span><spanclass="pre">Y)</span></code> : This specifies that we would like to read the result from <codeclass="docutils literal"><spanclass="pre">ch2</span></code> into variable <codeclass="docutils literal"><spanclass="pre">Y</span></code>. The character <codeclass="docutils literal"><spanclass="pre">r</span></code> is used here to make the syntax familiar to read syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.default()</span></code> : This is equivalent to the default in Go <codeclass="docutils literal"><spanclass="pre">select</span></code>. If none of the channels are ready for read or write, then the fluid code in the default block will be executed.</li>
@@ -42,7 +42,7 @@ The type *channel* is conceptually the blocking queue. In Go, its implemented i
The `select` operation has been in OS kernels long before Go language. All Unix kernels implement system calls *poll* and *select*. They monitor multiple file descriptors to see if I/O is possible on any of them. This takes O(N) time. Since Linux 2.6, a new system call, *epoll*, can do the same in O(1) time. In BSD systems, there is a similar system call *kqueue*. Go's Linux implementation uses epoll.
It might be a good idea to implement Fluid's select using epoll too. In this design doc, we start from the O(N) way, so we could focus on Python binding and the syntax.
It might be a good idea to implement Fluid's select using epoll too. In this design doc, we start from the O(N) way so that we could focus on Python binding and the syntax.
### Type Channel
...
...
@@ -87,79 +87,87 @@ The point here is that we need a consistent way to compose types, like in C++ we
### Send and Recv
In Go, we first create a channel as explained in the section above and then perform read and write operations on top of the channels.
Go's CSP implementation depends on data type *channel*. There are two types of channels:
```go
ch1 := make(chan int)
ch2 := make(chan int, 100)
```
1. The unblocked channel, or buffered channel, is a blocking queue with a non-zero sized buffer. The sending to buffered channel blocks if the buffer is full, and the receive operation blocks if the buffer is empty.
1. blocked channel, or unbuffered channel, is a blocking queue with no buffer. Both sending and receiving block with unbuffered channels.
To write (or perform a `Send` operation) the value of a variable `x`, to channel `ch1` above, we perform the following:
There are four types of actions with a channel:
```go
ch1 <- x
fmt.Println("Written to the channel")
```
Now to read (or perform a `Recv` operation) the value stored in `ch2` into a variable `y`, we perform the following:
1. Create a channel
```go
y <- ch2
fmt.Println("Received from channel")
```
```go
ch := make(chan int) // this is an unbuffered channel
ch := make(chan int, 100) // this is a buffered channel of 100 ints.
```
In Fluid, we should be able to perform the above operations on the channel objects as well. As of now, we support two different kinds of channels : [Buffered Channel](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h) and [UnBuffered Channel](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h)
1. Send
Send and Receive can be performed as following on a buffered channel:
Please be aware that a closed channel is not a nil channel, which is `var ch chan int`.
There are some [axioms with channels](https://dave.cheney.net/2014/03/19/channel-axioms):
# Read all the data from the channel
for i in xrange(3):
y = ch.recv()
1. A send to a nil channel blocks forever
# Done receiving , now close the channel
ch.close()
```
1. A receive from a nil channel blocks forever
1. A send to a closed channel panics
1. A receive from a closed channel returns the residual values and then zeros.
The send and receive operations will be similar for unbuffered channel as well, except for the fact that there is no buffer in an unbuffered channel, so the operations are completely synchronized. For example:
In Fluid, we have [buffered channels](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h) and [unbuffered channels](https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h)
The following program illustrates the Python syntax for accessing Fluid buffers.
```python
import threading
import fluid
buffer_size = 10
ch = fluid.make_channel(dtype=INT, buffer_size)
def send_to_channel(channel, data):
channel.send(data)
# Now write three elements to the channel
with fluid.while(steps=buffer_size):
fluid.send(ch, step)
fluid.close_channel(ch)
with fluid.while(steps=buffer_size):
fluid.print(fluid.recv(ch))
```
The following example shows that to avoid the always-blocking behavior of unbuffered channels, we need to use Fluid's goroutines.
```python
import fluid
# Create an unbuffered channel
ch = fluid.make_channel(dtype=INT)
# Writes and Reads are synchronous otherwise the calls will block.
In Go, the `select` statement lets a goroutine wait on multiple communication operations. A `select` blocks untill one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.
In Go, the `select` statement lets a goroutine wait on multiple communication operations. A `select` blocks until one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.
```go
...
...
@@ -202,9 +210,9 @@ with sel.default():
In the above code snippet, `X` and `Y` are variables. Now let us look at each of these statements one by one.
- `sel.case(ch1, 'w', X)` : This specifies that we are writing to `ch1` and we want to write the integer in variable `X` to the channel. The character `w` is used here to make the syntax familar to write syntax in Python I/O.
- `sel.case(ch1, 'w', X)` : This specifies that we are writing to `ch1` and we want to write the integer in variable `X` to the channel. The character `w` is used here to make the syntax familiar to write syntax in Python I/O.
- `sel.case(ch2, 'r', Y)` : This specifies that we would like to read the result from `ch2` into variable `Y`. The character `r` is used here to make the syntax familar to read syntax in Python I/O.
- `sel.case(ch2, 'r', Y)` : This specifies that we would like to read the result from `ch2` into variable `Y`. The character `r` is used here to make the syntax familiar to read syntax in Python I/O.
- `sel.default()` : This is equivalent to the default in Go `select`. If none of the channels are ready for read or write, then the fluid code in the default block will be executed.
<p>We also need Python wrappers for the above components.</p>
<p>The type <em>channel</em> is conceptually the blocking queue. In Go, its implemented is a <aclass="reference external"href="https://github.com/golang/go/blob/68ce117cf17b8debf5754bfd476345779b5b6616/src/runtime/chan.go#L31-L50">blocking circular queue</a>, which supports send and recv.</p>
<p>The <codeclass="docutils literal"><spanclass="pre">select</span></code> operation has been in OS kernels long before Go language. All Unix kernels implement system calls <em>poll</em> and <em>select</em>. They monitor multiple file descriptors to see if I/O is possible on any of them. This takes O(N) time. Since Linux 2.6, a new system call, <em>epoll</em>, can do the same in O(1) time. In BSD systems, there is a similar system call <em>kqueue</em>. Go’s Linux implementation uses epoll.</p>
<p>It might be a good idea to implement Fluid’s select using epoll too. In this design doc, we start from the O(N) way, so we could focus on Python binding and the syntax.</p>
<p>It might be a good idea to implement Fluid’s select using epoll too. In this design doc, we start from the O(N) way so that we could focus on Python binding and the syntax.</p>
<p>Go’s CSP implementation depends on data type <em>channel</em>. There are two types of channels:</p>
<olclass="simple">
<li>The unblocked channel, or buffered channel, is a blocking queue with a non-zero sized buffer. The sending to buffered channel blocks if the buffer is full, and the receive operation blocks if the buffer is empty.</li>
<li>blocked channel, or unbuffered channel, is a blocking queue with no buffer. Both sending and receiving block with unbuffered channels.</li>
</ol>
<p>There are four types of actions with a channel:</p>
<ol>
<li><pclass="first">Create a channel</p>
<divclass="highlight-go"><divclass="highlight"><pre><span></span><spanclass="nx">ch</span><spanclass="o">:=</span><spanclass="nb">make</span><spanclass="p">(</span><spanclass="kd">chan</span><spanclass="kt">int</span><spanclass="p">)</span><spanclass="c1">// this is an unbuffered channel</span>
<spanclass="nx">ch</span><spanclass="o">:=</span><spanclass="nb">make</span><spanclass="p">(</span><spanclass="kd">chan</span><spanclass="kt">int</span><spanclass="p">,</span><spanclass="mi">100</span><spanclass="p">)</span><spanclass="c1">// this is a buffered channel of 100 ints.</span>
</pre></div>
</div>
<p>To write (or perform a <codeclass="docutils literal"><spanclass="pre">Send</span></code> operation) the value of a variable <codeclass="docutils literal"><spanclass="pre">x</span></code>, to channel <codeclass="docutils literal"><spanclass="pre">ch1</span></code> above, we perform the following:</p>
<spanclass="nx">fmt</span><spanclass="p">.</span><spanclass="nx">Println</span><spanclass="p">(</span><spanclass="s">"Written to the channel"</span><spanclass="p">)</span>
<p>Now to read (or perform a <codeclass="docutils literal"><spanclass="pre">Recv</span></code> operation) the value stored in <codeclass="docutils literal"><spanclass="pre">ch2</span></code> into a variable <codeclass="docutils literal"><spanclass="pre">y</span></code>, we perform the following:</p>
<spanclass="nx">fmt</span><spanclass="p">.</span><spanclass="nx">Println</span><spanclass="p">(</span><spanclass="s">"Received from channel"</span><spanclass="p">)</span>
<p>In Fluid, we should be able to perform the above operations on the channel objects as well. As of now, we support two different kinds of channels : <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h">Buffered Channel</a> and <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h">UnBuffered Channel</a></p>
<p>Send and Receive can be performed as following on a buffered channel:</p>
<p>Please be aware that a closed channel is not a nil channel, which is <codeclass="docutils literal"><spanclass="pre">var</span><spanclass="pre">ch</span><spanclass="pre">chan</span><spanclass="pre">int</span></code>.</p>
</li>
</ol>
<p>There are some <aclass="reference external"href="https://dave.cheney.net/2014/03/19/channel-axioms">axioms with channels</a>:</p>
<olclass="simple">
<li>A send to a nil channel blocks forever</li>
<li>A receive from a nil channel blocks forever</li>
<li>A send to a closed channel panics</li>
<li>A receive from a closed channel returns the residual values and then zeros.</li>
</ol>
<p>In Fluid, we have <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/buffered_channel.h">buffered channels</a> and <aclass="reference external"href="https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/details/unbuffered_channel.h">unbuffered channels</a></p>
<p>The following program illustrates the Python syntax for accessing Fluid buffers.</p>
<p>The send and receive operations will be similar for unbuffered channel as well, except for the fact that there is no buffer in an unbuffered channel, so the operations are completely synchronized. For example:</p>
<p>In Go, the <codeclass="docutils literal"><spanclass="pre">select</span></code> statement lets a goroutine wait on multiple communication operations. A <codeclass="docutils literal"><spanclass="pre">select</span></code> blocks untill one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.</p>
<p>In Go, the <codeclass="docutils literal"><spanclass="pre">select</span></code> statement lets a goroutine wait on multiple communication operations. A <codeclass="docutils literal"><spanclass="pre">select</span></code> blocks until one of its cases can run, then it executes that case. It chooses one at random if multiple are ready.</p>
<p>In the above code snippet, <codeclass="docutils literal"><spanclass="pre">X</span></code> and <codeclass="docutils literal"><spanclass="pre">Y</span></code> are variables. Now let us look at each of these statements one by one.</p>
<ulclass="simple">
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch1,</span><spanclass="pre">'w',</span><spanclass="pre">X)</span></code> : This specifies that we are writing to <codeclass="docutils literal"><spanclass="pre">ch1</span></code> and we want to write the integer in variable <codeclass="docutils literal"><spanclass="pre">X</span></code> to the channel. The character <codeclass="docutils literal"><spanclass="pre">w</span></code> is used here to make the syntax familar to write syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch2,</span><spanclass="pre">'r',</span><spanclass="pre">Y)</span></code> : This specifies that we would like to read the result from <codeclass="docutils literal"><spanclass="pre">ch2</span></code> into variable <codeclass="docutils literal"><spanclass="pre">Y</span></code>. The character <codeclass="docutils literal"><spanclass="pre">r</span></code> is used here to make the syntax familar to read syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch1,</span><spanclass="pre">'w',</span><spanclass="pre">X)</span></code> : This specifies that we are writing to <codeclass="docutils literal"><spanclass="pre">ch1</span></code> and we want to write the integer in variable <codeclass="docutils literal"><spanclass="pre">X</span></code> to the channel. The character <codeclass="docutils literal"><spanclass="pre">w</span></code> is used here to make the syntax familiar to write syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.case(ch2,</span><spanclass="pre">'r',</span><spanclass="pre">Y)</span></code> : This specifies that we would like to read the result from <codeclass="docutils literal"><spanclass="pre">ch2</span></code> into variable <codeclass="docutils literal"><spanclass="pre">Y</span></code>. The character <codeclass="docutils literal"><spanclass="pre">r</span></code> is used here to make the syntax familiar to read syntax in Python I/O.</li>
<li><codeclass="docutils literal"><spanclass="pre">sel.default()</span></code> : This is equivalent to the default in Go <codeclass="docutils literal"><spanclass="pre">select</span></code>. If none of the channels are ready for read or write, then the fluid code in the default block will be executed.</li>
