Ryan Cavanaugh

@awerlogus I don't see any measurable difference between these issues. Certainly we would implement that flag as applying equally to both arrays and objects - are you saying we would...

I guess I'd like to understand what you think isn't effectively read-only about the type `[1, 2]`. You can write to it, but only in a way that doesn't change...

There are also lint rules which require trailing terminators, of course. It seems like if your lint configuration is going to be this picky, having fix-on-save would be a requirement...

I agree it's a duplicate but it really does suck. We should try again.

A shorter repro, if possible, would be greatly appreciated if you have some spare time. Thanks!

@rbuckton any idea what's up?

It's been a while so let me take a minute to explain why the current behavior is really suboptimal from a developer experience perspective. Let's say you write two different...

Yep, seems so. Thanks!

The existing `infer T` keyword produces a new binding for `T`; this wouldn't be available in argument positions (e.g. you can't write `getFoo()`). Having the `infer` keyword have arity 1...

Self-contained examples that don't assume importing/knowledge of rxjs would be very helpful