I think they’ll be gone. You can use raco decompile to check.
@lexi.lambda usually I use (quote blah) but I’m confident void works too
ok, thanks. checking with decompile is a good idea.
@lexi.lambda racket subscribes to the macro writers bill of rights iiuc, so you can consider not eliminating things like that to be bugs, I believe.
@robby what do you mean “macro writers bill of rights”? are you using that phrase as a metaphor or is there some document somewhere that says what macro writers can expect racket to handle gracefully when it comes to macro expansion?
It is by Kent Dybvig
there’s a talk somewhere on youtube about it IIRC
though tbh I remember finding that talk a little vague
I’m doing a lot of really weird things with syntax, and I have run into a quote-syntax: cannot use identifier tainted by macro transformation error, which unfortunately lists racket/private/stxcase as its source location. Is there any good way to debug these sorts of errors?
I remember running into them a while back, and I had no idea how to figure out where they were coming from in a large program.
Okay, now I’m even more confused. The error goes away if I replace a use of syntax with quote-syntax. Does syntax do something special I don’t know about related to taints/dye packs/other cute names?