# Structured Concurrency in Racket

**URL:** <https://trio.discourse.group/t/structured-concurrency-in-racket/226>\
**Category:** Structured concurrency\
**Created:** [October 9, 2019, 6:03pm UTC](https://trio.discourse.group/t/structured-concurrency-in-racket/226 "2019-10-09T18:03:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jab](https://yyz2.discourse-cdn.com/free1/user_avatar/trio.discourse.group/jab/32/100_2.png) [@jab](https://trio.discourse.group/u/jab)\
**Post date:** [October 9, 2019, 6:03pm UTC](https://trio.discourse.group/t/structured-concurrency-in-racket/226/1 "2019-10-09T18:03:45Z")

</div>

I started a thread by the same name in Racket-Users a couple days ago inquiring about the state of Structured Concurrency in Racket (and linked back to this forum for anyone there interested): [https://groups.google.com/forum/#!topic/racket-users/XHm\_1QFZPUI](https://groups.google.com/forum/#!topic/racket-users/XHm_1QFZPUI)

From that thread it looks like Structured Concurrency hasn’t made it to the Racket world yet, but it’ll be interesting to see if/how that changes in the future.

Just wanted to link to it from here for anyone interested.

---

<div class="post-metadata">

**Author:** ![njs](https://yyz2.discourse-cdn.com/free1/user_avatar/trio.discourse.group/njs/32/11_2.png) [@njs](https://trio.discourse.group/u/njs)\
**Post date:** [October 12, 2019, 8:31am UTC](https://trio.discourse.group/t/structured-concurrency-in-racket/226/2 "2019-10-12T08:31:40Z")

</div>

I just posted a reply in case anyone’s curious.

Happy Eyeballs is such a productive example… someone in the thread made an attempt at it, and their attempt had one of the standard mistakes that everyone’s first attempt has, so it gave me a perfect hook to hang my reply on.