You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears to me that the underscore syntax for specifying types and slurping arguments is in conflict when matching against macro calls. Consider the following MWE:
I went through the docs again and realized that there isn't a single example where one matches against a macro. I have been doing this for a while now but only encountered the underscore problem today. Is this kind of matching even supposed to work?
Yeah, I've bumped into this myself. I'd be interested in seeing a PR for this, but OTOH, I'm reluctant to make changes to the plumbing behind a significant chunk of the ecosystem, in case that we mess it up. I guess we'd have to see if the PR can be simple and "obviously right".
It appears to me that the underscore syntax for specifying types and slurping arguments is in conflict when matching against macro calls. Consider the following MWE:
Indeed, if you look at the
@macroexpand
output then the_
incode_warntype
triggers aMacroTools.TypeBind
:I went through the docs again and realized that there isn't a single example where one matches against a macro. I have been doing this for a while now but only encountered the underscore problem today. Is this kind of matching even supposed to work?
This appears on
[email protected]
.The text was updated successfully, but these errors were encountered: