I was thinking the parameter could be a handy runtime switch, defaulting to "safe". However realistically there's probably a lot of other ground to cover when it comes to "debug" vs. "production" deployments. Maybe this needs a more comprehensive approach than nibbling away one switch at a time.
Maybe a doc warning is sufficient: "It is probably unwise to put this information in a network response (like a web page) in production." -- 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.
