The macro-debugger collection contains two tools: a stepper for macro expansion and a standalone syntax browser. The macro stepper shows the programmer the expansion of a program as a sequence of rewriting steps, using the syntax browser to display the individual terms. The syntax browser uses colors and a properties panel to show the term’s syntax properties, such as lexical binding information and source location.
This module provides expand-like procedures that allow the user to specify macros whose expansions should be hidden.
Warning: because of limitations in the way macro expansion is selectively hidden, the resulting syntax may not evaluate to the same result as the original syntax.
|(expand-only stx transparent-macros) → syntax?|
|stx : any/c|
|transparent-macros : (listof identifier?)|
Macros can explicitly send information to a listening macro stepper by using the procedures in this module.
|(emit-remark fragment ... [#:unmark? unmark?]) → void?|
|fragment : (or/c syntax? string?)|
|unmark? : boolean? = #t|
By default, syntax objects in remarks have the transformer’s mark applied (using syntax-local-introduce) so that their appearance in the macro stepper matches their appearance after the transformer returns. Unmarking is suppressed if unmark? is #f.
(define-syntax (mymac stx) (syntax-case stx () [(_ x y) (emit-remark "I got some arguments!" #'x "and" #'y) #'(list 'x 'y)])) (mymac 37 (+ 1 2))
(Run the fragment above in the macro stepper.)
The id argument acts as the step’s “macro” for the purposes of macro hiding.
|(expand/step-text stx [show?]) → void?|
|stx : any/c|
|(stepper-text stx [show?]) → (symbol? -> void?)|
|stx : any/c|
The stepper presents expansion as a linear sequence of rewriting process, and it gives the user controls to step forward or backwards as well as to jump to the beginning or end of the expansion process.
If the macro stepper is showing multiple expansions, then it also provides “Previous term” and “Next term” buttons to go up and down in the list of expansions. Horizontal lines delimit the current expansion from the others.
Macro hiding lets one see how expansion would look if certain macros were actually primitive syntactic forms. The macro stepper skips over the expansion of the macros you designate as opaque, but it still shows the expansion of their subterms.
The bottom panel of the macro stepper controls the macro hiding policy. The user changes the policy by selecting an identifier in the syntax browser pane and then clicking one of “Hide module”, “Hide macro”, or “Show macro”. The new rule appears in the policy display, and the user may later remove it using the "Delete" button.
The stepper also offers coarser-grained options that can hide collections of modules at once. These options have lower precedence than the rules above.
Macro hiding, even with no macros marked opaque, also hides certain other kinds of steps: internal defines are not rewritten to letrecs, begin forms are not spliced into module or block bodies, etc.
The selection is indicated by bold text.
The user can click on any part of a subterm to select it. To select a parenthesized subterm, click on either of the parentheses. The selected syntax is bolded. Since one syntax object may occur inside of multiple other syntax objects, clicking on one occurrence will cause all occurrences to be bolded.
The syntax browser displays information about the selected syntax object in the properties panel on the right, when that panel is shown. The selected syntax also determines the highlighting done by the secondary partitioning (see below).
The primary partition is indicated by foreground color.
The primary partitioning always assigns two syntax subterms the same color if they have the same marks. In the absence of unhygienic macros, this means that subterms with the same foreground color were either present in the original pre-expansion syntax or generated by the same macro transformation step.
Syntax colored in black always corresponds to unmarked syntax. Such syntax may be original, or it may be produced by the expansion of a nonhygienic macro.
Note: even terms that have the same marks might not be bound-identifier=? to each other, because they might occur in different environments.
The user may select a secondary partitioning through the Syntax menu. This partitioning applies only to identifiers. When the user selects an identifier, all terms in the same equivalence class as the selected term are highlighted in yellow.
When the properties pane is shown, it displays properties of the selected syntax object. The properties pane has two tabbed pages:
If the selection is an identifier, shows the binding information associated with the syntax object. For more information, see identifier-binding, etc.
Displays source location information and other properties (see syntax-property) carried by the syntax object.
The binding information of a syntax object may not be the same as the binding structure of the program it represents. The binding structure of a program is only determined after macro expansion is complete.
|module-name : module-path?|
- 'keep module at phase (optional-comment)
The require must be kept because bindings defined within it are used.
- The optional comment indicates if the require must be kept
only because its bindings are re-exported
only because the whitelist DB says so
- 'bypass module at phase
The require is used, but only for bindings that could be more directly obtained via another module. For example, racket can be bypassed in favor of some subset of racket/base, racket/contract, etc.
- 'drop module at phase
The require appears to be unused. Unless it must be kept for side effects or for bindings of a very unusual macro, it can be dropped entirely.
(check-requires 'typed-scheme) (check-requires 'unstable/markparam) (check-requires 'macro-debugger/syntax-browser/widget)
A scripting interface to macro-debugger/analysis/check-requires usable from the command-line is available at macro-debugger/analysis/check-requires-script.rkt.
Example (from racket root directory):
racket -l macro-debugger/analysis/check-requires-script \ collects/syntax/*.rkt
|module-name : module-path?|