Leaf Petersen

I don't think it's a particularly bad idea to omit the name - we added that ability for a reason. An extension without a name is private to the library...

> I do like that you're pushing on this +1 This is a very useful discussion.

I think this is already specified [here](https://github.com/dart-lang/language/blob/master/accepted/future-releases/nnbd/feature-specification.md#implicit-conversions). Feel free to re-open if I've missed something.

> It is specified there for non-nullable expressions and nullable/non-nullable context types, and only for callable object tear-off and double literals. > > That does not cover nullable expressions and...

For reference, [this](https://github.com/dart-lang/language/issues/401) is the issue where discussed this previously.

For `double` conversion, I think this is already implicitly specified: ``` If \code{double} is assignable to $T$ and \code{int} is not assignable to $T$, then the static type of $l$...

More relevant background [here](https://github.com/dart-lang/sdk/issues/39710).

@escamoteur No, we've not revisited this. It seems like something that we might want to look into at some point (evaluate how breaking changing it would be, and if reasonable,...

I'm not sure what the proposal here is. @munificent seems to be suggesting in discussion in #2484 that this is about allowing general expressions in patterns, but I'm not sure...

@lrhn I think what's not clear to me is what you mean by "expressions". The example you use is just a variable (I think), which is fine syntactically - that's...