Re: [racket-users] Making expanded bindings visible in top-level

2020-09-06 Thread Sage Gerard
Ah, thank you. I didn't think that the original syntax object would have the lexical information I needed. For some reason I thought about constructing a syntax object using the name pattern variables and using that instead. ~slg ‐‐‐ Original Message ‐‐‐ On Sunday, September 6, 2020 10:

Re: [racket-users] Making expanded bindings visible in top-level

2020-09-06 Thread Sorawee Porncharoenwase
I think it’s only enough to fabricate the #%info-* identifiers. For example, in the file you linked above, you can add: [#%info-domain (datum->syntax stx '#%info-domain)] to with-syntax, and provided that you provide #%top-interaction, you should be able to use #%info-domain in the REPL. On Sun,

[racket-users] Making expanded bindings visible in top-level

2020-09-06 Thread Sage Gerard
I'm writing a variant of [setup/infotab](https://github.com/racket/racket/blob/master/racket/collects/setup/infotab.rkt) to allow `#%top-interaction' plus some other bindings of my choice. But when I create a evaluator in the context of such a module, `#%info-domain' and `#%info-lookup' are not