Ryan Cavanaugh

@markerikson correct - reverted in both 4.8 final and ongoing in `main`. Hopefully a fix can be found that satisfies both use cases. @Andarist done 👍

Quasi-approved. We like this idea a lot, but need a working implementation to try out to understand all the implications and potential edge cases. Having a sample PR that at...

https://github.com/Microsoft/TypeScript/issues/1213#issuecomment-96854288 is still the current state of it. I don't see anything here that would make us change the priority of the feature.

It's clearer what's going on here if you separate out the intermediate expression: ```ts const m = foo[key]; m.nested = { a: 1 }; ``` The type of `m` is...

Correct Functions types will unify a bit better; demo speaks louder than words ```ts const foo = { x: { nested: { a: 1 }, setNested(_a: {a: number}) { }...

👀👀👀👀👀👀👀👀👀👀

@sheetalkamat / @rbuckton thoughts on what we might do here?

keep it broken so people stop writing types like that

The CI runs a second pass to ensure that TypeScript can still build itself after any proposed change. You introduced build errors into `shims.ts`, as shown on the PR page...

See #32758