Slava Egorov

> I don't understand. The arguments never have to be constants right? Only the type arguments denoting the native types have to be. The example you give is normal tuple...

> Unfortunately, I don't think it's entirely simple to implement. At least two challenges are I know are: FWIW you list design challenges, not implementation challenges. The feature as I...

> Try that with `Enum e = .foo..index.toRadixString();` As I have said before: I would be totally fine shipping something that only works in parameter positions, lists and on the...

> It really won't fly if `Enum x = .foo;` works and `Enum x = test ? .foo : .bar;` does not. I don't really understand why it has to...

Why not follow established convention and add a method `copyWith()` to the tuple? ``` cpoint = cpoint.copyWith(color: Color.red); ``` The method would be a bit magical (not expressible in normal...

I am wondering if long purely positional ("nameless") tuples are antipattern to begin with - I don't think neither `with (_, _, _, _, 5)` nor `tuple with {4: value}`...

I think dart2js (/cc @rakudrama) is always more impacted by changes like these, because their type representation is modularised enough for them to treeshake things at finer granularity. VM does...

I think if we make them to behave as extensions (as in: look at the static type of the receiver rather than actual reified runtime type), then `nonvirtual` is a...

@srawlins do you have any artifacts from UX review? I'd be curious to read the motivation. Stable seems much cleaner to me than either dev or beta, so there must...

> I agree that the stable screenshot is cleaner, but I think it'd be even cleaner if there was literally just one line per result (and no headers in the...