Bob Nystrom

> So far, I've never had to use a single record, but I wrote tons of sealed classes and patterns inside switches. I could be wrong, but I suspect that...

> they set me up for a situation where the type of the value being matched changes and instead of a static error the condition just silently fails to match....

> I also added a `Map.pairs` extension to the `collection` package in [dart-archive/collection#289](https://github.com/dart-archive/collection/pull/289) The nice thing about `Map.pairs` versus this issue is that it lets you rename the variables more...

This looks really nice. In particular, I have sometimes wanted to have an if condition that is a chain of `case` and/or other conditional tests like: ```dart if (thing case...

> Rust just... does this. "Just" is doing a lot of work in this sentence. :) Rust compiles generic code using monomorphization: you get a full separate copy of the...

It's definitely not a priority. I think it probably came up because we just migrated the language/identity tests which have some tests around strings and `identical()` that are more precise...

Now that augmentations don't need to support every possible thing a macro could want to do, I think we have the opportunity to simplify a bit here. Here's a proposal:...

I went ahead and scraped a pub corpus to see how common various kinds of constructors are: ``` -- Constructor (233346 total) -- 107272 ( 45.971%): generative ============== 56758 (...

> If people really, really like to use default values for documentation, I'd go for the last. Let's see... Looking at individual constructor parameters: ``` -- Default (632449 total) --...

> If we only allow one augmenting declaration to provide _implementation_, then I think we should just consider default values (like initializing formals and `super` parmeters) a part of _implementation_....