Khairul Azhar Kasmiran

Hi, it's been more than a week. You can verify this fix yourself using `diff -u` on before/after perf files to see whether lines containing ` __libc_start| LazyCompile | v8::internal::|...

Yes, different rule sets can be enabled in an overrides entry -- they can even have different parsers. For example, for `*.ts` files, it would be `@typescript-eslint` rules with the...

And from my testing, it does seem viable to have something like: ```ts const config: Linter.Config = { // ... }; ``` if the rule typings need to be extended...

Ping @pmdartus @j-f1 @saadq @JasonHK @bradzacher @JounQin ... apparently @typescript-bot doesn't do reminders for this particular situation

Well there can be more than two sets of rule typings (e.g. for `eslint`, `@typescript-eslint` and `jsonc`) that need to be concatenated together so I think using `&` as seen...

Anyway whether or not `&` or `,` is better, the config `Rules` typings should still be propagated to the `overrides` property so that some rules typings support is available even...

I would be really surprised if this change causes massive ecosystem effects.

Ready to merge

A possible fix is #2385 but it was deemed too complicated for the given purpose. You might want to resurrect it and simplify it perhaps.

Since `readelf` provides the same functionality, I don't think I'll resolve this anytime soon.