> On Jun 13, 2019, at 6:43 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote:
>
>
> Oh, don't do that. Unreliable workarounds to concurrency problems
> really do come back to bite you later.
To ask the second dumbest possible question, what error-recovery policies are
reliable under concurrency? (Put another way, what guarantees exist about
errors under concurrency? E.g. can we trust that all errors will trigger an
exception?)
And the dumbest possible: if there are no such policies, then how can you ever
be certain the code works?
--
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/07C94517-FA0B-46A7-949D-0AB3179A2F70%40mbtype.com.
For more options, visit https://groups.google.com/d/optout.
