So far from this thread, it seems the idea of Structured Concurrency hasn’t yet made it into the Racket world. I’ll be interested to see if it gets adopted in Racket in the future (or at least better understood) as its adoption grows elsewhere.
In the meantime, in case it helps illustrate the idea to anyone else still interested, check out the talk I linked to previously showing an implementation of Happy Eyeballs using structured concurrency. Or just read it directly from the Trio source once you understand what a nursery and a cancel scope are: https://github.com/python-trio/trio/blob/master/trio/_highlevel_open_tcp_stream.py (RFC 6555 Happy Eyeballs is like a Hello World of the problem space that structured concurrency is addressing, so this is an illustrative example.) If there is some blessed Racket implementation of Happy Eyeballs, it could be useful to compare – for correctness, completeness, obviousness, and elegance. -- 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/ed325f57-d7e3-47dc-a2e7-76fc0af1ff50%40googlegroups.com.
