Re: [racket-users] Macros that conditionally generate code

This reminds me of a similar thread on Slack yesterday. When a macro `define`s something, it's usually better for everyone if the identifier is supplied to the macro. It's nicer for you as the macro writer because you don't need to think so hard about scope and hygiene. And it's nicer for the

Re: [racket-users] Macros that conditionally generate code

On Wed, Mar 6, 2019 at 11:31 PM Sorawee Porncharoenwase wrote: > > Isn’t this because of hygienity in general? *headdesk* Of course. Thanks, I should have recognized that. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from

Re: [racket-users] Macros that conditionally generate code

Isn’t this because of hygienity in general? For example: #lang racket (define-syntax (foo stx) (syntax-case stx () [(_) #'(define doubleup 1)])) (foo) doubleup ; unbound id doesn’t define doubleup. While the below code does: #lang racket (define-syntax (foo stx) (syntax-case stx ()