Boshen

We also need to align implementation with esbuild, since that's what we have been doing.

> I assume this depends on #611 / #1164 so can't be tackled yet? Seems so. You can always look at the source, e.g. https://github.com/eslint/eslint/blob/1bf2520c4166aa55596417bf44c567555bc65fba/lib/rules/no-misleading-character-class.js#L7

> But is the idea that spans always specify positions as UTF16? Or spans specify both UTF8 and UTF16 positions? Or one or the other depending on user choice? This...

Closing issue for house keeping, the umbrella issue is used for tracking individual rules.

> Sorry, I've written you an essay again. If you're short on time, the important question is this one: > > > Should Span's current start and end be changed...

By looking at https://github.com/eslint/eslint/blob/main/lib/rules/no-misleading-character-class.js ... are we able to implement this @leaysgur? We may need to mark this as not supported :-/

I just found another use case for the line / column problem https://github.com/oxc-project/oxc/blob/19577709dbcfc9761cfcb1b39ec7f3ebdc810285/crates/oxc_language_server/src/linter.rs#L392-L399

These problems are some low hanging fruits, we don't need to tackle these problems right now. It's just good to know these problems exist when we code in Rust (UTF8),...

> This will soon be the only blocker for being able to use OXC as a parser for TS, I hope there is a way to to this in performant...

> The TextEncoder thing is working. Didn't yet measure the perf impact, as soon as it was on I started getting new inetresting diff 😅. Sadly the current one involves...