Ryan Cavanaugh

> Anyway, I'm going to stop trying to argue my point here. I'm a bit disappointed with the offhanded dismissal of my proposal – it does not feel like there...

It's not really possible to make this in a way that's both useful and sound. Consider a function like ```ts declare function fn(s1: string, s2: string): void; declare function fn(n1:...

I don't recall offhand what the assignability rules are around overload targets. I would have said "assignable to each" but that's clearly not what's going on.

The code generation here is as-expected; the bug is the lack of error message to flag the use-before-init.

Parameter properties are considered to be sugar for a `this.e = e` assignment in the constructor.

Would take a PR to improve the error message but I don't understand the use case very much. What kind of enums would be backed by bigints?

I've pitched something like this internally a few times and gotten a lukewarm reception. I think the key is figuring out some way to really scope this down to something...

One reason I advocate for removing `noImplicitUseStrict` is that no one ever can remember what it actually does, which based on reading the description I wrote up there, includes me...

Summarizing decisions from the meeting: **Queued for deprecation**: `noImplicitUseStrict `, `target: es3`, `keyofStringsOnly`, `suppressExcessPropertyErrors`, `suppressImplicitAnyIndexErrors`, `noStrictGenericChecks`, `charset`, `out` **Still alive**: All `module` targets (usage of these, based on GitHub queries,...

Duplicate #42388