Boshen

> But after that, what do you think should be highest priority? After some consideration, let's put a milestone on `prettier-oxc-parser`. I don't have the time and energy to work...

https://github.com/eslint/eslint/blob/main/lib/rules/no-useless-backreference.js This doable.

> I want to give a try Go ahead! Please report progress so other contributors don't end up doing the same thing. i.e. which routine and which arch are you...

Previous attempt on padding the source: * https://github.com/oxc-project/oxc/issues/43 * https://github.com/oxc-project/oxc/pull/90 --- > http://0x80.pl/articles/simd-byte-lookup.html I can help contact Wojciech Muła on twitter if we have questions to ask.

Yeah it makes more sense now, we can give it another try.

> @Boshen @overlookmotel Do you have a benchmark setup or framework? The current setup is only observable with codspeeed on github linux machines. I think we need another github repository...

> Any plans to add [eslint-plugin-perfectionist](https://github.com/azat-io/eslint-plugin-perfectionist) rules? It is becoming quite popular, 1.5 K stars. Just looking forward to fully migrate to amazing and promising OXC stack! This rule fits...

> @Boshen I just thought: Does the irregular whitespace linter rule need to catch irregular whitespace in comments too? Or can they be ignored? > > What about in strings?...

https://github.com/evanw/esbuild/blob/cc74e6042a9f573bf58e1e3f165ebda70af4ad3b/internal/js_printer/js_printer.go#L281

Codegen now prints useful comments such as jsdoc, vite / webpack specials, pure annotations. The remaining issue is print *all* comments, which is really difficult, I'll revisit them when requirements...