On Jul 5, 2015, at 10:56 PM, Benjamin Gruenbaum wrote:
> So, following work on RegExp.escape [1] I found out that implementations may
> extend the regular expression grammar in JavaScript [2]. However, when asking
> esdiscuss and Stack Overflow about it [2][3] it doesn't look like any
> implem
Benji -- but you've just specifically mentioned that implementations
are already using the flexibility provided by the spec to experiment
with and implement ES6 features. Why are you going to foreclose that
possibility for ES2016+?
The perl community has managed to compatibly extend their regex e
This isn't really about `RegExp.escape` as an issue. We can always extend
`RegExp.escape` when we make additions to the RegExp grammar as a standard
that would not be a problematic issue since we can keep both parts in sync
relatively easily.
On the other hand currently implementations are allowed
I think it would be more worthwhile of we tried to draw a compatibility
boundary. Taking perlre as a baseline, for example, are there additional
characters we should escape in `RegExp.escape` so that implementations (and
the language itself) could add more perlre features without breaking
compatib
So, following work on RegExp.escape [1] I found out that implementations
may extend the regular expression grammar in JavaScript [2]. However, when
asking esdiscuss and Stack Overflow about it [2][3] it doesn't look like
any implementations currently do so (*).
Can we please forbid implementations
5 matches
Mail list logo
