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
This commit introduces a new `regex-syntax` crate that provides a
regular expression parser and an abstract syntax for regular
expressions. As part of this effort, the parser has been rewritten and
has grown a substantial number of tests.
The `regex` crate itself hasn't changed too much. I opted for the
smallest possible delta to get it working with the new regex AST.
In most cases, this simplified code because it no longer has to deal
with unwieldy flags. (Instead, flag information is baked into the AST.)
Here is a list of public facing non-breaking changes:
* A new `regex-syntax` crate with a parser, regex AST and lots of tests.
This closes#29 and fixes#84.
* A new flag, `x`, has been added. This allows one to write regexes with
insignificant whitespace and comments.
* Repetition operators can now be directly applied to zero-width
matches. e.g., `\b+` was previously not allowed but now works.
Note that one could always write `(\b)+` previously. This change
is mostly about lifting an arbitrary restriction.
And a list of breaking changes:
* A new `Regex::with_size_limit` constructor function, that allows one
to tweak the limit on the size of a compiled regex. This fixes#67.
The new method isn't a breaking change, but regexes that exceed the
size limit (set to 10MB by default) will no longer compile. To fix,
simply call `Regex::with_size_limit` with a bigger limit.
* Capture group names cannot start with a number. This is a breaking
change because regexes that previously compiled (e.g., `(?P<1a>.)`)
will now return an error. This fixes#69.
* The `regex::Error` type has been changed to reflect the better error
reporting in the `regex-syntax` crate, and a new error for limiting
regexes to a certain size. This is a breaking change. Most folks just
call `unwrap()` on `Regex::new`, so I expect this to have minimal
impact.
Closes#29, #67, #69, #79, #84.
[breaking-change]
0 commit comments