Lasse R.H. Nielsen

The way dot-shorthands work is based on the context type. If you can pass type arguments, then it's boo longer using the context type, but (presumably) another installation of the...

I can see that there are places where a `Foo` is asked for, but you want to provide a `Foo()` instead, or multiple inside a collection like here. I'm not...

I don't think it's worth pushing it right now. We have enough on our plate for the release. It's a feature that can be safely added later since it introduces...

One thing you can do is ```dart entryIndex!; // Promotes to non-null entryIndex++; // Now works. ```

Comments, in no particular order. 1. About: > In order to avoid surprising effects, it is a compile-time error if an instantiation yields a declaration where an occurrence of an...

> What do we do if a name parameter does not resolve to anything? I think I'd prefer to not allow a templated name to occur freely in the template....

This is mainly a library issue, not a language issue, but it intersects with the language specification if it has to say anything about these new types. So, do they...

It's definitely going to be the same people making the decision, whether it's a library or language change, the only difference is whether it requires a language specification change. Unless...

`Uint16List`, etc., already exist. That's why I don't see much need for a standalone `Uint16` type, because the case where you really need to care about memory layout, long repetitions,...

If you only have one uint8 in your class, it won't change anything. All the other fields, and the object, will be 8-byte aligned anyway. You need to have multiple...