| Age | Commit message (Collapse) | Author |
|---|
|
https://github.com/ruby/prism/commit/aee2de91a3
|
|
https://github.com/ruby/prism/commit/ccc746f918
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11753
|
|
https://github.com/ruby/prism/commit/498dd922d4
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11741
|
|
https://github.com/ruby/prism/commit/fd58d6a9ea
|
|
https://github.com/ruby/prism/commit/976a3cd0a5
|
|
https://github.com/ruby/prism/commit/988ac82187
|
|
https://github.com/ruby/prism/commit/509ff88e92
|
|
https://github.com/ruby/prism/commit/b624e09cc6
|
|
When we encounter an invalid unicode escape within a regular
expression, we now pass that error on to Onigmo as if it didn't
exist in the parser (which matches the upstream parser's behavior).
We do this because there are tests that specify that you are
allowed to have invalid Unicode escapes if they are within the
context of a regular expression comment for a regular expression
in extended mode. That looks like:
/# \u /x
Note that this _only_ applies to Unicode escapes (as opposed to
applying to hex or meta/control escapes as well). Importantly it
also only applies if the regular expression is terminated. An
unterminated regular expression will still get error handling done
in the parser. That would look like:
/# \u
that would result in the same error handling we have today.
https://github.com/ruby/prism/commit/fb98034806
|
|
https://github.com/ruby/prism/commit/9f1f7d08bd
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11234
|
|
https://github.com/ruby/prism/commit/4cc0eda4ca
|
|
https://github.com/ruby/prism/commit/fb7e1ebb7f
|
