> On Jun 15, 2019, at 8:31 AM, Robby Findler <ro...@cs.northwestern.edu> wrote: > > Place channels are asynchronous, not syncronous (i.e. you don't have > two-way rendez-vous). So the call to put returns immediately in > `loopback-p` before the other end receives the result. And now the > next iteration of the loop's get is in parallel to the put from the > previous iteration's.
Are place channels "Buffered Asynchronous Channels"? [1] Or just a similar idea? The `place` docs describe place channels as "endpoints for a two-way buffered communication" and "asychronous" [2] but there is no link to BAC, which makes me think they are different. But reading your description of the behavior of place channels with `sync` and `handle-evt`, now I'm not sure. [1] https://docs.racket-lang.org/guide/concurrency.html?q=channels#%28part._.Buffered_.Asynchronous_.Channels%29 <https://docs.racket-lang.org/guide/concurrency.html?q=channels#(part._.Buffered_.Asynchronous_.Channels)> [2] https://docs.racket-lang.org/reference/places.html?q=places#%28tech._place._channel%29 <https://docs.racket-lang.org/reference/places.html?q=places#(tech._place._channel)> -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/C4E43B34-A41D-4A0D-8FC1-D5E0BF377D34%40mbtype.com. For more options, visit https://groups.google.com/d/optout.
