Stephen Adams

@stereotype441 I think the positional access syntax should work when the receiver has static type `dynamic` to exactly the same degree as it will for named fields. If we decide...

> and even then the implementation teams didn't bother to take advantage of it Compiling a Dart `switch` statement to a JavaScript `switch` statement _is_ taking advantage of it. Otherwise...

> **In other words, just removing this restriction is pay as you go WRT existing switches, but does remove a performance rail. @rakudrama** do you agree with this summary, or...

> We also make it so that https://github.com/dart-lang/language/issues/1512. That is, if the parameter has a default value, passing null explicitly also triggers parameter getting the value of the default value...

> As I see it, it might actually help on some platforms... I don't think it helps is the way you suggest. Many (perhaps most) optional arguments are named, so...

I find it slightly surprising that this does not work. Promotion of a local would happen if you manually desugared ```dart if (foo?.something != null) ... ``` to ```dart if...

I think the proposed cure of removing adjacent strings is worse than the problems it is trying to solve. We already have lints that are effective at preventing some of...

There has not been much discussion here about making more constructors `const`. I recently want a const `String.fromCharCode` and `String.fromCharCodes`.

Consider adding `toInt` and `toDouble` for `num` receivers.

The advice extends to `Set.of` and `Map.of`. @a14n: Yes, we should change that `List.from` to `List.of`. That code dates back to Dart 1 before there was a `List.of`, and the...