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
When endOfLine is used after or, the initial close paren introduced by or is erased.
I could take a shot at fixing this. How do we want the above example to be interpreted, as /^(?:abc|def)$/gm or as /^(?:abc|def$)/gm? Now that I think of it, this might have been a feature and not a bug due to this ambiguity. If so, it should be documented.
The text was updated successfully, but these errors were encountered:
For example,
throws the following error
This traces to how
_suffixes
is handled.When
endOfLine
is used afteror
, the initial close paren introduced byor
is erased.I could take a shot at fixing this. How do we want the above example to be interpreted, as
/^(?:abc|def)$/gm
or as/^(?:abc|def$)/gm
? Now that I think of it, this might have been a feature and not a bug due to this ambiguity. If so, it should be documented.The text was updated successfully, but these errors were encountered: