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.
On Wed, Nov 30, 2016 at 1:30 PM, Dan Liebgold <[email protected]> wrote: > On Tuesday, November 29, 2016 at 6:30:08 PM UTC-8, David K. Storrs wrote: >> >> Can you simply catch it and handle it inside the thunk? >> > > That's probably best. I was looking at the machinery to serialize exceptions > in type racket* and thinking I needed that.... > > > *: > https://github.com/racket/typed-racket/blob/master/typed-racket-test/send-places.rkt > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Jay McCarthy Associate Professor PLT @ CS @ UMass Lowell http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
