Erik Ernst

That's very interesting information, @munificent, thanks! > It seems that `null` appears fairly often in both then and `else` branches, though the `else` branch is ~2/3 of them. If the...

> so the aesthetics of the syntax matters Right, but I wasn't saying "don't introduce `if` expressions", I was saying "if we do introduce `if` expressions then there's a proposal...

> The text seems to use the type of `e2` before it's inferred, so type inference of `e2` depends on type inference of `e2`. No, we're not using the type...

The notion of "find the least element in the set of possible types obtained by type inference on `e2`" needs some amount of scrutiny (and it's new to the type...

Good point! ;-)

For the for-in case, https://github.com/dart-lang/language/issues/4584 is relevant. An idea mentioned there is that we simply treat `final item` and `var item` as iteration variable such that the iterable receives `_`...

@srawlins wrote: > I _must_ declare two constructors then, and one of them _must_ not be usable. I hope, if and when we actually introduce primary constructors to the language...

The `primary` keyword on a constructor in the body of the declaration which was mentioned in the original posting is already included in the proposal about primary constructors, [here](https://github.com/dart-lang/language/blob/main/working/2364%20-%20primary%20constructors/feature-specification.md#:~:text=%3CmethodSignature%3E%20%3A%3A%3D%0A%20%20%20%20%20%27primary%27%3F%20%3CconstructorSignature,constructorSignature%3E%20(%3Credirection%3E%20%7C%20%3Cinitializers%3E)%3F%3B). So...

We don't need (and we actively want to avoid) a specific constructor declaration, but we _must_ declare it. However, we can give it a private name, and then it's almost...

@lrhn wrote: > it's a great reminder that vases are breakable, and a way for you to break it, should you really need to. In some cases I might be...