On 05/03/18 15:28, 'Paulo Matos' via Racket Users wrote: > > Is there anything I can try to improve backtrace generation? >
OK, doing racket -l errortrace -t <prog> as suggested in http://docs.racket-lang.org/errortrace/quick-instructions.html helps. Does errortrace introduce a performance penalty or simply adds debug information ala -g in traditional compilers? -- Paulo Matos -- 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.
