Bob Nystrom

Moving this over to the language repo because this is an ambiguity in the actual language feature and not a parser bug. We'll have to change the proposal to handle...

One idea is to put `Record` at the beginning of record types, like: ```dart class C { @deprecated Record(int, int) pair; } @foo Record(int, int) Function(int) bar; ``` I don't...

Another (probably bad) idea: We could extend the language to support named *type* parameters. That could arguably be useful for other user-defined generic types because (as with optional named parameters)...

> Would using `#(` for types, but not for expressions, open up the possibility for record type literals? Yes, it would. > If we use either `#(` or `Record` do...

> I think it should have one. Me too! > The recordExpression must have a static type which is an actual record type (not dynamic and not Record or T...

> I really do not want the `DestructureN` interfaces. I'm not particularly attached to them, but they do seem to solve the problem that I want to solve which is...

I'm moving this over to patterns-later. I definitely want it, but I think it would be really hard to get this designed and into the initial release.

Thanks for filing this. There's also [this unfilled section in the proposal](https://github.com/dart-lang/language/blob/master/working/0546-patterns/patterns-feature-specification.md#type-promotion) whose body is just a TODO. :)

For the most part, the style guide isn't based on what's better *in principle*, it's based on what most Dart users agree is best. There are a number of Dart...

We deliberately don't have guidance on this yet because we're still waiting to get enough user experience to figure out what the best practice is. Right now, I don't think...