00:03 <kengruven> i'm writing a client API. is there a conventional approach in racket to managing async calls/responses? for now i'm making all calls take a callback arg, and then have my library keep a hash of {request_id -> callback_fn}, and then run a thread to wait for all responses and dispatch them to the correct callback. this seems a little awkward to me but i'm new to racket so i'm not sure what feature might make it more natural.

00:27 <shawnw> Use continuations to build a coroutine system.

00:29 <shawnw> https://docs.racket-lang.org/more/index.html has an example

01:45 <kengruven> ah, thanks for the pointer.

13:50 <Putonlalla> I submitted a report about the `match` problem. https://github.com/racket/racket/issues/4799