Lasse R.H. Nielsen

I noticed that we have *a lot* of occurrences in the platform libraries (which includes some of the oldest Dart code in existence, so not entirely surprising). Some clean-up will...

If (when!) we don't allow abstracting over pattern width, you can't get a single typed `wait` that handles different widths. So yes, we'd need `wait2`, `wait3`, ..., `wait22`. ***HOWEVER*** (use...

Like the extensions, hate the dynamic typing being necessary. Also doesn't scale well with named record elements. A more direct approach, without using `Future.wait`, would be: ```dart extension FR2X on...

Constructor parameter lists are more complicated than field declarations, and users want to have complete control over whether things are named or not, and in which order they occur. Fields...

I think `final`-by-default is correct for a `data class`. They must be immutable to be safely unboxable (#2362). Inferring the fields from the constructor does not preclude adding `final` to...

We can definitely allow `class` declarations to have `late` variable declarations in the normal way, but I don't think I'd want them in the primary constructor. Why be `late` when...

If we add a `const` modifier to parameter and return types of a function declaration, with the meaning that the corresponding argument and return expressions *must* be constant expressions, which...

If you want `int add(const int a, const int b) ...` to return a constant, we're closer to #2222 or generalized constant evaluation (like what @munificent was working on before...

That comes back to our definition of mixin application - are we copying, or allowing the same member to occur in more than one library. (And then there's the `covariant`...

As historical curiosity, the Dart spec used to say: > Dart source text is represented as a sequence of Unicode code points normalized to Unicode Normalization Form C. from version...