Closed gus-massa closed 1 year ago
I believe the issue here is that there are (probably too) large buffers in the IO implementation. So the stop/kill button actually did stop the work that was being done to figure out which bytes to print, but large number of bytes that were already put into the queue and are being processed by DrRacket (instead of the user's program) don't stop. So probably something needs to be improved here.
See also https://github.com/racket/racket/issues/1677. That issue also talks about the problematic interaction between read
and display.
If you run this
or
it takes too long to print.
While it is printing, if you click the Stop/Kill button, it changes but it does not stop or kill the process.