Boshen
Boshen
> External consumers of OXC in Rust may also want UTF-8 offsets. The linter is our external consumer, although it lives inside this repository. There are also people using the...
> What purpose do these external tools require UTF-8 spans for? Current usages so far are just slicing text for diagnostics, which are all on the cold path.
> Do you envisage the same is true for other external consumers? I can't think of anything else besides source maps 🤔
Let me iterate on this tomorrow.
I'll find sometime to figure out recreating scopes and bindings during visits, probably this weekend.
After going back and forth with all the requirements and solutions, I propose that we don't over-engineer this, keep it simple and accept the performance regression. The tasks will be...
https://github.com/oxc-project/oxc/blob/main/crates/oxc_linter/src/rules/eslint/no_undef.rs is currently under nursery.
I thought I saw your name somewhere before but never recalled until you mentioned that swc PR. I had numerous discussions with different people and we all concluded that AST...
Here are my requirements after some research and thoughts: * Change UTF-8 to UTF-16 span positions * Serialize to estree for maximum ecosystem compatibility * Target a valuable use case...
Closing issue for house keeping, the umbrella issue is used for tracking individual rules.