Jacob MacDonald

The fact that the "name" of a positional `this.` parameter today is the private name isn't really relevant because nobody has to care about the name outside of your package....

> Also what should happen if I have both - a and _a member? This would just be an error, you can't have two parameters with the same name. We...

The renaming here only happens for _private this. constructor parameters_. That is still potentially breaking (when it comes to positional parameters) but we can roll it out with language versioning...

The String name is also not really a good way of serializing an Enum value, usually I would use the index. It would feel pretty weird to me for us...

The example of a nullable but required parameter is imo a very valid use of `null` and should be a pattern that is still allowed. It is quite a lot...

> just embrace that nullable means optional But there are cases where this isn't the desired API. Fwiw, I would be fine with making nullable optional by default, and non-nullable...

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 something else...

https://github.com/dart-lang/language/issues/1988 is also relevant and could provide a nice way for tooling to treat "strings" as dart code.

> On the other hand there is a natural mapping from QQ constructed ASTs to source code on the disk so for debugging purposes it should be simply possible to...

> * Execution layer: debugging generated code. In QQ case compiler can generate a file on the side which contains all generated code. Note that this file does not have...