The errortrace/errortrace-lib module exports all of the exports of errortrace, plus a few more. It does not install any handlers.
The additional exports are as follows:
(errortrace-compile-handler stx immediate-eval?) → compiled-expression? stx : any/c immediate-eval? : any/c
Compiles stx using the compilation handler that was active when the errortrace/errortrace-lib module was executed, but first instruments the code for Errortrace information. The code is instrumented only if
is the same as when the errortrace/errortrace-lib module was executed. This procedure is suitable for use as a compilation handler via current-compile.
Produces a compile handler that is like errortrace-compile-handler, except that the code that it produces is instrumented if the value of
is the same as when the original thunk is invoked.
Displays information about the exception; this procedure is suitable for use as an error display handler.
Macro-expands and instruments the given top-level form. If the form is a module named errortrace-key, no instrumentation is applied. This annotation function is used by errortrace-compile-handler.
Like errortrace-annotate, but given an explicit phase level for stx; (namespace-base-phase) is typically the right value for the phase-level argument.
Unlike errortrace-annotate, there no special case for a module named errortrace-key. Also, if stx is a module declaration, it is not enriched with imports to explicitly load Errortrace run-time support.