Slava Egorov

I feel like bundling these two features together does not actually bring us any benefit. I can see some parallels between them - but `struct` being reified and `extension struct`...

> That is, I'm not very comfortable with a world in which there are three unrelated declaration forms in play here, e.g.: I agree with this sentiment. I was rotating...

My vote would be against extending concrete structs. My question here would be: what could be a real-world use-case for extending concrete structs? Cause I am struggling to figure out...

I think `struct`'s should be immutable (all fields implicitly `final`). "Updating" structs which appear within mutable classes is supported by the `f = f.copyWith(field: newValue)` pattern (which compilers are free...

I totally agree that this syntax should be applicable to classes as well. You can make an argument that it is good enough if it only supports simple cases, e.g....

> We'd need to give you a way to opt out of being a const constructor if you don't want it. FWIW I think that majority of Dart developers don't...

I think we should avoid `struct` because this keyword is rather overloaded and means different things in other languages (e.g. C# and C++ has mutable structs), it also clashes with...

QQ is an interpolation of sorts - it is just interpolation of structured program representation rather than strings. Having QQ does not change expressivity of metaprogramming system, but rather makes...

@jakemac53 > What would the execution model be in Dart for a feature like this? It seems like maybe an interpreter would make the most sense, or did you have...

> I'm not particularly fond of the tokens USD for opening/closing code blocks. I am just using `-{...}` and `+{...}` because those are the ones I am familiar with. They...