Bob Nystrom

> I'd prefer something like `final` or `sealed` which is more familiar in the OOP world (see like Java, C#, Delphi, Kotlin etc...) Yeah, I considered that, as we could...

> @munificent is there a reason that someone might want `closed` but not `base`? Yes, I think so. This is essentially what you get in other languages by exposing a...

There are a couple of separate pieces here that I want to try to tease out to understand better. That way we can be more precise about what the actual...

Unary records used to be in the proposal and I took them out. They caused some disagreement around whether a unary record is isomorphic to its field or not. Likewise,...

Definitely, there are always ways to avoid the ambiguity. Parenthesizing an expression or removing a newline is usually sufficient. The issue is more around whether the user finds those ambiguities...

> I saw a lot of JavaScript projects and it feels like scratching your eyes, when there is semicolon on one string, and there is no on the next similar....

I did a bunch more investigation of optional semicolons after writing the "Terminating Tokens" proposal. I wrote up my thoughts on the experience [here](https://github.com/dart-lang/language/blob/master/resources/optional-semicolons-prototype.md).

> It's clear that there are few opponents. Yes, I think most users *want* us to eliminate the semicolons. The hard point is designing a method for *how* to do...

That's good data to have, but is somewhat confounded: * (As far as I know) it only polls existing Flutter users, so has survivorship bias. * It frames it in...

> prevent them from progressing. I don't think this is the right mental model to have. The language doesn't progress spontaneously on its own. It requires a lot of hard...