I think this is a pretty good overview of the "stock" choices: https://docs.racket-lang.org/guide/concurrency.html
On Fri, Mar 22, 2019 at 8:21 AM George Neuner <gneun...@comcast.net> wrote: > Message passing avoids most share locking issues, so it is better to > implement that way when possible. I agree. Usually I start with a channel or async-channel. And usually that turns out to be all I think need. If you really need to, you can build things using semaphores, but that's tricky and I'd suggest something like: http://greenteapress.com/wp/semaphores/ -- 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. For more options, visit https://groups.google.com/d/optout.
