undefined | Better HN

0 pointsbad_user9y ago0 comments

> async channels are special cases of sync channels

You got it the other way around - synchronous is a special case of asynchronous, because any synchronous result or stream can be processed asynchronously, but for having guaranteed synchronous results you're adding restrictions. And going the other way, from async to sync is not possible without blocking threads, which is an error prone, platform specific hack. Take the possibility of blocking threads away and you'll notice the true nature of these models.

0 comments

eulerfx2349y ago

In CML/Hopac, async channels (buffers) are implemented in terms of sync channels - there is not async channel primitive built in. Synchronization is the essence of this model. When an operation is waiting on a matching communication through a channel, it is suspended, but no OS thread is blocked.

But yes, going from async to sync requires blocking, which is why CML/Hopac takes the approach of making sync the core primitive.

j / k navigate · click thread line to collapse

0 pointsbad_user9y ago0 comments

> async channels are special cases of sync channels

0 comments

eulerfx2349y ago

But yes, going from async to sync requires blocking, which is why CML/Hopac takes the approach of making sync the core primitive.

j / k navigate · click thread line to collapse