Re: [racket-users] filesystem-change-evt and thread-suspend

2016-11-14 Thread Philip McGrath
Thanks very much for the quick workaround (and ultimately for the repair) — it's always a relief to know I haven't overlooked some detail! On Monday, November 14, 2016 at 9:30:17 AM UTC-6, Matthew Flatt wrote: > No, that's not supposed to happen. I've pushed a repair. > > > I was able to

Re: [racket-users] filesystem-change-evt and thread-suspend

2016-11-14 Thread Matthew Flatt
No, that's not supposed to happen. I've pushed a repair. I was able to replicate the problem on Mac OS X, and it looks like the problem with filesystem events is specific to that platform. But the filesystem-event problem is due to a more general bug in the scheduler, and the same bug shows up

[racket-users] filesystem-change-evt and thread-suspend

2016-11-13 Thread Philip McGrath
Hi everyone, I've been trying to get to know Racket's threads and particularly filesystem-change-evt, and I've come to a point of confusion. I thought that a filesystem-change-evt's synchronization result was supposed to be the event itself, which it is most of the time, but in combination