The documentation for syntax properties states that if a macro sets a syntax property during expansion then instead of the expanded syntax having only the set value, it has a cons tree containing that value and any previous values set for that same property. As I understand it, this means it's impossible for macros to remove syntax property values during expansion. Why is that? I don't understand the purpose of it, and it makes working with custom syntax properties a bit unpleasant API-wise.
-- 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.
