Lasse R.H. Nielsen

Who will we be helping by allowing this? I'd rather properly disallow it, so people who are putting bad or meaningless values into collections will stop doing that. And maybe...

If the class is generic, this issue has no impact. A type variable is not statically the `void` type.

Decision is to allow the cases listed here, and disallow `[?e]`, `{?e}`, `{?e:_}` and `{_:?e}` where `e` has type `void`. The latter are also currently allowed, but do not match...

Records are a little different from collections. They're more like "multiple independent values in a single chunk" than they are a *collection* of values. They're just for passing values around....

I'm a little afraid of having too many meanings of the same operator. Also, it's not clear to me which one is `== null` and which is `!= null`, so...

We probably can't use `e1 ?? e2 : e3` because it would be ambiguous. The expression `{e1 ?? e2 : e3}` is already a map literal `{(e1 ?? e2) :...

The current plan is to allow `parentMap?.['href'] ?? defaultValue`. The feature is planned as part of the non-nullable type feature.

You can write that operator today, you just don't get any promotion. ```dart extension on Object? { bool operator ~() => this != null; } ``` The philosophical objection to...

If that's the alternative, then I wouldn't try to avoid the `if`. That's a cure that's worse than the illness. Just write ```dart if (variable != null) use(variable); ``` It's...

> don't you find it strange … No. The `?`/`:` syntax is an expression which must have a value. You cannot omit one of the branches, because then it doesn't...