tinygo/testdata/channel.txt

len, cap of channel: 1 2 false
len, cap of channel: 0 0 false
recv from open channel: 1 true
received num: 2
received num: 3
slept
received num: 4
received num: 5
received num: 6
received num: 7
received num: 8
recv from closed channel: 0 false
complex128: (+7.000000e+000+1.050000e+001i)
sum of n: 149
sum: 25
sum: 29
sum: 33
sum(100): 4950
deadlocking
select no-op
after no-op
sum: 5
did send one
select one n: 0
select n from chan: 55
select n from closed chan: 0
select send
sum: 235
non-concurrent channel recieve: 1
non-concurrent channel recieve: 2
closed buffered channel recieve: 3
closed buffered channel recieve: 4
closed buffered channel recieve: 0
hybrid buffered channel recieve: 2
blocking select sum: 3
runtime: add cap and len support for chans 5 years ago			`len, cap of channel: 1 2 false`
compiler: implement comparing channel values 6 years ago			`len, cap of channel: 0 0 false`
compiler: add support for channel operations Support for channels is not complete. The following pieces are missing: * Channels with values bigger than int. An int in TinyGo can always contain at least a pointer, so pointers are okay to send. * Buffered channels. * The select statement. 6 years ago			`recv from open channel: 1 true`
			`received num: 2`
			`received num: 3`
			`slept`
			`received num: 4`
			`received num: 5`
			`received num: 6`
			`received num: 7`
			`received num: 8`
			`recv from closed channel: 0 false`
compiler: allow larger-than-int values to be sent across a channel Instead of storing the value to send/receive in the coroutine promise, store only a pointer in the promise. This simplifies the code a lot and allows larger value sizes to be sent across a channel. Unfortunately, this new system has a code size impact. For example, compiling testdata/channel.go for the BBC micro:bit, there is an increase in code size from 4776 bytes to 4856 bytes. However, the improved flexibility and simplicity of the code should be worth it. If this becomes an issue, we can always refactor the code at a later time. 6 years ago			`complex128: (+7.000000e+000+1.050000e+001i)`
compiler,runtime: implement stack-based scheduler This scheduler is intended to live along the (stackless) coroutine based scheduler which is needed for WebAssembly and unsupported platforms. The stack based scheduler is somewhat simpler in implementation as it does not require full program transform passes and supports things like function pointers and interface methods out of the box with no changes. Code size is reduced in most cases, even in the case where no scheduler scheduler is used at all. I'm not exactly sure why but these changes likely allowed some further optimizations somewhere. Even RAM is slightly reduced, perhaps some global was elminated in the process as well. 5 years ago			`sum of n: 149`
compiler: add support for channel operations Support for channels is not complete. The following pieces are missing: * Channels with values bigger than int. An int in TinyGo can always contain at least a pointer, so pointers are okay to send. * Buffered channels. * The select statement. 6 years ago			`sum: 25`
			`sum: 29`
			`sum: 33`
			`sum(100): 4950`
all: implement trivial select statements Implement two trivial uses of the select statement. Always blocking: select {} No-op: select { default: } Go 1.12 added a `select {}` instruction to syscall/js, so this is needed for Go 1.12 support. More complete support for select will be added in the future. 6 years ago			`deadlocking`
			`select no-op`
			`after no-op`
compiler,runtime: implement non-blocking selects Blocking selects are much more complicated, so let's do non-blocking ones first. 5 years ago			`sum: 5`
compiler,runtime: implement stack-based scheduler This scheduler is intended to live along the (stackless) coroutine based scheduler which is needed for WebAssembly and unsupported platforms. The stack based scheduler is somewhat simpler in implementation as it does not require full program transform passes and supports things like function pointers and interface methods out of the box with no changes. Code size is reduced in most cases, even in the case where no scheduler scheduler is used at all. I'm not exactly sure why but these changes likely allowed some further optimizations somewhere. Even RAM is slightly reduced, perhaps some global was elminated in the process as well. 5 years ago			`did send one`
compiler,runtime: implement non-blocking selects Blocking selects are much more complicated, so let's do non-blocking ones first. 5 years ago			`select one n: 0`
			`select n from chan: 55`
			`select n from closed chan: 0`
			`select send`
			`sum: 235`
Improved blocking (#513) core: major improvements to blocking, including support for buffered channels. 5 years ago			`non-concurrent channel recieve: 1`
			`non-concurrent channel recieve: 2`
			`closed buffered channel recieve: 3`
			`closed buffered channel recieve: 4`
			`closed buffered channel recieve: 0`
			`hybrid buffered channel recieve: 2`
add blocking select 5 years ago			`blocking select sum: 3`