You might also find the redex model and examples from the scope sets paper useful:
http://www.cs.utah.edu/plt/popl16/ On Monday, August 6, 2018 at 5:18:47 PM UTC-4, michael.ballantyne wrote: > > As far as I'm aware, the new expander was tested initially on the simple > cases in: > > https://github.com/racket/racket/blob/master/racket/src/expander/demo.rkt > > The `racket-tests-core` tests here: > https://github.com/racket/racket/tree/master/pkgs/racket-test-core/tests/racket > > particularly `stx.rktl`, `macro.rktl`, and perhaps `module.rktl`. > > and by simply attempting to expand `racket/base`, `racket`, the rest of > the standard library, and ultimately every package on the package server. > > I'm not sure many of these would make easy smoke tests for a hygienic > expander proposal, as many are quite specific to racket's syntax, > libraries, and choice of fancy expander APIs. > > > > On Monday, August 6, 2018 at 4:32:08 PM UTC-4, Mitchell Wand wrote: >> >> Is there a test suite for the macro expander? I assume that you must >> have one, but it would save me some effort if somebody can tell me where it >> is. >> >> I'm interested in finding out if you have good corner cases for testing a >> proposal for a hygienic expander. >> >> --Mitch >> >> -- 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.
