Slava Egorov

> Why is it important to prevent the `dynamic get call => this;` stack overflow? Is anyone writing that and expecting different behavior? +1 to this question. (There is one...

@lrhn I see. Thanks - this makes sense to me. I was looking at it from the perspective of `d()` and `d.call()` being equivalent to each other, but I can...

> Does `d.call()` mean and behave like `d.call.call()`? `(d.call)()` behaves like `d.call.call()`. But `d.call()` and `d.call.call()` are unrelated.

@lrhn @eernstg can you label the issue? It is unclear to me if this is tool issue or a language issue. Thanks.

The short answer is: you can't avoid manually forwarding the properties. Dart does not have a way to abstract over parameter/argument lists and say "this function has all parameters of...

Thank you for your thoughts @Ing-Brayan-Martinez. As has already been explained above this is not the right place for this sort of discussion, so I am going to close this...

> Not sure precisely which use-cases to cover, but since kind of quote/quasi-quote-like syntax for delimited Dart code, evaluating to a Code object, is a possibility. Yeah, using functions for...

Changes to `identity` behavior and `copyWith` semantics as described in that proposal can't be implemented through macros. Macros can help generating the boilerplate though.

Thanks to everyone for the initial feedback. I have done some major rewrite removing things which complicated the proposal (e.g. treatment of generics and functions) from the proposal. I have...

I have some small tweaks here and there and just going to land this.