[racket-users] How to set up rackunit tests to test the REPL?

Hi, What are the recommended ways to create unit tests that test *both* run *and* REPL (#%top-interaction)? *Background:* I created a custom language and have some unit tests. My updated language passed all unit tests. After delivery, a client ran into a bug that only happens in REPL. I could

[racket-users] [module announce] in-out-logged

Package: https://pkgs.racket-lang.org/package/in-out-logged Wraps a chunk of code in "entering" and "leaving" log messages, returns the value(s) produced by the code. Example: Keyword arguments are all optional. #:to and #:at may appear in either order but #:with must come last if it is

Re: [racket-users] Why does syntax-parser work here but not syntax-parse?

*headdesk headdesk headdesk headdesk headdesk* Thank you. On Wed, Sep 8, 2021 at 2:02 PM Stephen Chang wrote: > > shouldn't the entire parenthesized expression be given to the macro > processor and then replaced with something valid before being rejected? > > That would be true if you're

Re: [racket-users] Why does syntax-parser work here but not syntax-parse?

> shouldn't the entire parenthesized expression be given to the macro processor > and then replaced with something valid before being rejected? That would be true if you're defining a macro, i.e. if you use `define-syntax` instead of `define`. > > -- > You received this message because you are

[racket-users] PLDI 2022 First Call for Papers

Please distribute widely. *Call for Papers* 2022 ACM Conference on Programming Language Design and Implementation (PLDI) Mon 20 - Fri 24 June 2022 San Diego, California, United States https://pldi22.sigplan.org/track/pldi-2022-pldi#Call-for-Papers PLDI is a premier forum for

[racket-users] Why does syntax-parser work here but not syntax-parse?

This is from the documentation and it obviously works: (define parser1 (syntax-parser [((~alt (~once (~seq #:a x) #:name "#:a keyword") (~optional (~seq #:b y) #:name "#:b keyword") (~seq #:c z)) ...) 'ok])) (parser1 #'(#:a 1)) When run it yields 'ok. If I

[racket-users] Is there a way to format keys/values like raise-arguments-error

raise-arguments-errors produces neatly stacked key/value pairs with whitespace arranged such that values line up even when keys are of different lengths. Is there an easy way to get that for something that is not an error? I've been through both The Printer and the raise-arguments-error sections