Boshen
Boshen
Let's do this incrementally with proper testing, we can cherry-pick some of the code from [Maneren's branch](https://github.com/Maneren/oxc/tree/regex) My requirements: 1. 100% test coverage 2. Good documentation 3. use the same...
@Ubugeeei Nice work! I hope your are learning a lot.
@Ubugeeei is too busy with other stuff (vapor mode I guess?). Feel free to assign this to yourself @IWANABETHATGUY
@IWANABETHATGUY have you started working on this?
@maurice it seems like @IWANABETHATGUY is working on it, I'll let him coordinate the tasks.
Linting regexp may be doable without a parser, but it'll definitely be easier to lint by visiting an AST. I still want to regex parser for oxc for maximum performance...
cc @manzt
@leaysgur The current blocking task is the parser, we can always distribute the linter rules to future contributors. You don't need to implement the linter rules like you did with...
> Is a Lexer necessary? Probably not, since there is no whitespace or semi colons like JavaScript. We can try one without a lexer. > Support for strict mode (annexB)...
@leaysgur Do you intend to start from scratch? You can start from a new branch by coping over some of the code from https://github.com/oxc-project/oxc/pull/2030 Once you have something, I'll help...