Lasse R.H. Nielsen

I'm not opposed to specifying that we want valid UTF-8 as input to our compilers, I'm just not convinced it needs to be part of the *language* specification. I would...

What does it *mean* to extend a view/extension struct. Presumably it means that you include the extended view's methods and add your own on top (whether overriding or not). That...

What if we introduced method forwarding in general, in a way that also applies to classes. ```dart class Something implements Foo { FooBar x; // ... export x { //...

The usual argument against this is that it makes a distinction between a user written getter and a getter introduced by a final field. Making that distinction locks the original...

It's unclear to me how or when you call the named mixin application's `initState` or `dispose` methods. There are two of them, both do a `super`-call, but nobody calls them....

So, these named mixins will work like normal mixins except that *some of* their declarations are "namespaced" to avoid conflict with other mixin declarations of the same name. It can't...

So the override would apply only to the methods of specific interfaces/types, any other members would not be visibile. That sounds like the ability to hide members from an interface...

> > I would prefer to not add such functions outside of dart:mirrors, and then they would be part of a RecordMirror, not something which works on the reified tuple...

Out existing supertypes have funcitonality. `Enum` has `int get index;` and `Function` has a magic `call`. `Record` likely will not have any interface members. (It *might* have abstract `==` and...

If `Record` is a (proper) supertype of `Object?`, then every object is a record (which fair, it's a one-positional-element record, and `Record` is really `Object?*`, using the Kleene star). We'd...