On Wednesday, November 30, 2016 at 10:38:05 AM UTC-8, Jay McCarthy wrote: > The typed-racket code returns a value from the job, whereas this code > assumes the job is fully self-contained. Perhaps job-queue should > protect itself from job exceptions. >
Probably a good idea. I got confused working on my thunk... I'm spawning a subprocess that errors out. I was using an asynchronous spawn (process/ports) and it caused a silent hang in (stop-job-queue! jq). I switched to system* for other reasons and since that is synchronous is handles the exception differently such that it never escapes my thunk ... so things work. -- 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.
