provides ways to circumvent unexpected type bindings #160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes issues involved with the syntaxes to specify expression types.
Currently,
@capture
and@match
can't distinguish between their syntaxto specify a
:head
ofExpr
and a variable name with underscores.For example, in the example below,
@capture
recognizesglobal_string
as the syntax to specify
Expr
's head (i.e.:string
), not as a simplevariable name:
Since an expression can really have an arbitrary head,
@capture
macrocan't really distinguish them (while we can do some assertion when the
syntax to specify atomic expression type, though).
This PR implements new macros
@capture_notb
and@match_notb
, whichignore all the expression type matching syntaxes and provide the ways to
circumvent the issue described above:
These changes aren't breaking but they're somewhat a big change, I'd
like to minor version bump.