Leaf Petersen

cc @mit-mit @lrhn @eernstg @chloestefantsova @johnniwinther @munificent @stereotype441 @natebosch @jakemac53 @rakudrama @srujzs @sigmundch @rileyporter @mraleph

> With that, I'd also say that any other generative constructor _must_ be redirecting (eventually) to the primary constructor. > Since the primary constructor initializes all fields. Not sure I...

> Compare that to what you'd get using the current proposal: This is assuming no changes to documentation conventions, which I think is not realistic. From a brief look at...

@ lrhn > We'd need to give you a way to opt _out_ of being a `const` constructor if you don't want it. You may not want it if you...

> I think that's generally going to be too fragile. I'd recommend you having to write `const` to get a `const` constructor, say: > > ```dart > const class Foo(int...

> It's not that we can introduce an identical struct later, it's more that we can't even know that we can present the same struct twice. I don't point this...

We may wish to start emitting a warning in the next release that this is going away.

> Yes, I'm on board with this. Maybe we should carve it out as a separate proposal since the main patterns one already has a lot of surface area? I'd...

I see that @lrhn has a proposal for this [here](https://github.com/dart-lang/language/issues/2321).

cc @mit-mit @lrhn @eernstg @chloestefantsova @johnniwinther @munificent @stereotype441 @natebosch @jakemac53 @rakudrama @srujzs @sigmundch @rileyporter @mraleph