Mateus Felipe C. C. Pinto

> I would prefer not using `_` since we are already using `_` heavily in a lot of places to mean "not used" in the context of lambdas. > This...

> > Ironically, we are making wildcards first-class in the language > > Which I am in favour of! > But I thought that would rather make this proposal impossible...

Not even I can infer what you want `T` to be.

The first line of the error you posted seems to indicate that the compiler, just like me, can't infer what `T` is supposed to be.

Yeah, I like this gradual changes proposal. I only would change the last step to completely disallow "extending" mixins, as we will be going to Dart 3.0, where breaking changes...

Seems like this is a duplicate of #3552, although this one seems more like a question than a request.

> That works, but i rather not have to declare a new variable, on a new line to have the analyzer conclude it is not null. With a guard statement...

I would love to have `unless`. It would be specially useful with patterns, as we can't do something like `if (a case! pattern)` or `if (a case !pattern)`.

I know this proposal is not directly related to this, but if we are ever going to have `protected` members, we should probably want to deal with `private`. As you...

> Protecting against the same author, who can change the code, it's not as big a priority. Having class private declarations is more about avoiding accidental name clashes between implementation...