suzanne.soy/debug-scopes
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

doc: replace undefined module name #6

Merged
bennn merged 1 commits from fix-tag into master 2019-12-17 18:37:53 +00:00
Conversation 1 Commits 1 Files Changed 1 +3 -2
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
scribblings/debug-scopes.scrbl
View File

@ -43,7 +43,8 @@
(foo (list 123))] (foo (list 123))]
When using @racketmodname[debug-scopes/named-scopes], a named scope is often When using named scopes---for example, via
@racketmodname[debug-scopes/named-scopes/override]---a named scope is often
used instead of the macro scope flipped by @racket[syntax-local-introduce]. If used instead of the macro scope flipped by @racket[syntax-local-introduce]. If
@racket[+scopes] is called within that context, it also annotates the whole @racket[+scopes] is called within that context, it also annotates the whole
expression with the named scope which acts as a replacement for the macro expression with the named scope which acts as a replacement for the macro
@ -167,4 +168,4 @@ hack currently used to implement named scopes.
@orig:syntax-local-introduce, but uses the named scope set up by @orig:syntax-local-introduce, but uses the named scope set up by
@racket[define-syntax] if called within the dynamic extent of a call to a @racket[define-syntax] if called within the dynamic extent of a call to a
macro defined by the overridden @racket[define-syntax] (and otherwise behaves macro defined by the overridden @racket[define-syntax] (and otherwise behaves
like the original @orig:syntax-local-introduce).} like the original @orig:syntax-local-introduce).}