Lasse R.H. Nielsen

> it is not obvious which purpose an operator [] on the type bool would have, and I doubt it would ever occur. [\*cough\*]( https://github.com/dart-lang/language/issues/4519#issuecomment-3328968509) That particular usage would not...

Allowing `if` expressions should be easy. An `if` statement would take precedence in expression statements, an `if` element would take precedence in element contexts, but otherwise we'd just allow `if...

One worry would be that this is special to the switch expression, which might be confusing. Doing `switch ((x, y, z)) { .... }` works, but `var triple = (x,...

Using the union-free type will give be the **NonNull** I have wanted. I don't know if removing a `FutureOr` is always desired. If you do `maybeFutureOr ?? Future(...)`, then you...

> The notion of "find the least element in the set of possible types obtained by type inference on `e2`" needs some amount of scrutiny That sound probable. It seems...

> Would it be possible to fix the for loop variable Anything is possible, but this one is a different issue. The problem here is that the expression has a...

I think the instance will be an `A`. (Doesn't mean that there is no problem. There definitely is.) If you do `new A.n1()`, the `new` operator allocates the object, not...

It's not impossible to allow. It is indeed always available at compile-time, and there is no way it can possibly not be. You're not allowed to override or hide the...

If you think of the header-part of an extension type as part of its syntax, more than as a constructor declaration, then it might be more palatable for you. It's...

If it's a private hammer that only you can access, it's a great reminder that vases are breakable, and a way for you to break it, should you really need...