Lasse R.H. Nielsen

I can see the argument for "a supertype of subtypes of `A`" that isn't intended to be concrete. It's not something you can implement from scratch, but you can attach...

My main worry about making names of positional parameters significant, is that existing code wasn't written for it, and after the feature has launched, changing those names is a breaking...

This is something we did think about designing super-parameters, but decided to at least punt on. I believe the proposed syntax at the time was just `super`, so: ```dart class...

Ignoring positional arguments is always a hard sell to me, because I very rarely use named parameters. They're just too cumbersome to be worth it in almost all cases. I...

Maybe not a reserved word, but at least a built-in identifier, since it works as a prefix for types. That said, the name would have to be one that is...

Type variable promotion came up in a discussion about [promoting `this`](https://github.com/dart-lang/language/issues/1397). When you do `if (this is C)` inside `class C` you are asking whether `T` is a subtype of...

What you want is probably to ask whether `T` *implements* the interface `int`, which `Never` doesn't, it's "just" a subtype. Checking `T` is a proper supertype of `Never` is one...

One argument against a generic `Type` was that if we ever got an "existential open" or "type parameter pattern" (which I personally hope we will), it allows you to convert...

The parser is probably very happy that `class` is a reserved word. If it sees `final class` it knows it's not seeing the start of a variable declaration. If we...

It's sometimes a very fitting name when you're writing a compiler. Or, more widely relevant, a macro.