Ryan Cavanaugh

We don't do type-directed emit, which is what this is asking for. `jsx: react` doesn't have the `key` special-casing; it's more accurately thought of as the JSX semantics of ~2016...

Please open a new issue with a concrete repo if you're encountering problems.

@ppoulard we don't really want to change decorator semantics right now (especially in a way that allows previously-unallowed things) since there are proposals working through the TC39 committee to standardize...

Why didn't the bot put any labels on this?

Agreed; `through` has been in archive mode for 7 years, this is not likely to be worth the risk

It's worse than this; there's a tsc ordering sensitivity as well originating in the same problem ```ts declare let cv: HTMLCanvasElement | OffscreenCanvas; declare let oc: OffscreenCanvas; // Swapping these...

Here's a reduced version that doesn't need the DOM types ```ts interface Alpha { foo(type: "num", opts?: unknown): number; foo(type: "str", opts?: unknown): string; foo(type: string, opts?: unknown): number |...

Further reduced. Will provide more commentary later ```ts interface Alpha { foo(n: "str", opt?: boolean): string; } // Comment/uncomment to change errorness type B = Beta['foo']; interface Beta { foo(n:...

I was going to try to simplify @gabritto's comment but I think it already is as simple as it gets, modulo the slightly simpler example above. There are basically only...

Yep, thanks. I'll have to see if this repros in the Go codebase