for the first problem, you've found a bug in the Racket CS thread
scheduler (i.e., Racket BC behaves correctly in this case). Suspending
a thread that is sleeping didn't prevent the thread from being woken up
on its previous schedule. I've pushed a repair as commit 7a12b4ac93.
After fixing that bu
I'm experimenting with using custodians to manage threads (on Racket 7.8
[cs]) and encountering behavior I don't understand.
I start a looping thread `t1` under a new custodian `c1`.
I then shutdown `c1` and expect `t1` to stop looping. If I started `t1`
with `thread` then this expectation is
2 matches
Mail list logo
