Bob Nystrom

> I don't see any obvious pitfalls. I'd be sad to lose a reserved word that might end up being useful for a future language feature.

> Of the languages you mention above: JavaScript, Java, Go, Python, Ruby, Rust, C, and Swift, hour many can you actually remember the syntax for octals in? Or that they...

> Only DateTime seems legit (though hardcoded dates must be uncommon other than it tests). Maybe that's the use case for `0d`? I would bet money that the number of...

I've significantly simplified the augmentations proposal (#4357) by getting rid of `augmented`, augmenting (non-`abstract`) variables, and most of the ugly corners around augmenting constructors. But as it currently stands, the...

> Why? The _definition_ of `abstract final int x;` is that it introduces (and is indistinguishable from the declaration of) the getter `int get x;`. Right, but at least the...

OK, we discussed this at the language meeting and we're OK with using `abstract` and allowing abstract variables to be augmented. Yes, it sends a kind of confusing signal to...

Yeah, I think Lasse's argument makes sense. Treating `augmented` as special only inside the members where it actually is special is consistent with how `await` works too: ```dart main() {...

> Wouldn't it suffice to say the following?: > > Consider a local variable declaration declaring just one element (which could be a pattern declaring several variables, or a regular...

> #2714 reports a grammar ambiguity, but also proposes rules about how to disambiguate a pattern which is a plain identifier. Issue #2714 suggests specifying the grammar differently but unless...

With #4357, this isn't relevant any more. Variables (late or not) can't be augmented.