On Sat, Mar 5, 2016 at 8:09 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > If you start DrRacket fresh or create a new tab and paste > > (define (total n) > (for/sum ([x (in-range (+ 1 n))]) x)) > (time (total 1000000000)) > > into the interactions window, then it runs at non-debugging speed. > After clicking "Run" (with an empty program), the interactions window > runs the example with debugging speed. > > That difference seems confusing, and it might explain why some had > trouble seeing the example run slowly.
I think this is a bug in the behavior of DrRacket, separate from any lack of transparency. I've made an attempt at a fix and pushed it. On Wed, Mar 2, 2016 at 10:25 PM, Neil Van Dyke <n...@neilvandyke.org> wrote: > Alex Harsanyi wrote on 03/02/2016 11:19 PM: >> >> If it cannot be improved, perhaps a warning message should be printed in >> the eval window... > > I like this idea. Maybe add to the DrRacket REPL banner, the > debugging/instrumentation options that are enabled. I've pushed something that uses these strings, put onto the name of the language as shown in the REPL. Is that what you had in mind? Does it seem helpful? (module-language-repl-no-annotations "") (module-language-repl-debug-annotations ", with debugging") (module-language-repl-debug/profile-annotations ", with debugging and profiling") (module-language-repl-test-annotations ", with test coverage") Robby -- 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. For more options, visit https://groups.google.com/d/optout.
