Simon Krajewski

> I can see why this needs further explaining. Why would it need to override test_T however??? The parent technically doesn't overload so it shouldn't be renamed. Right, adding `overload`...

I don't think this could be implemented without significant changes to how we handle default values. In our implementation, the default values are not part of the function type, but...

Look, I'm not making this up to annoy you or avoid implementing this feature. You can look at haxe/macro/Type.hx and verify for yourself that the only place default values show...

I added that because we wanted to have the original syntax for generating documentation. For generating output, we need a properly typed representation and we cannot store that in metadata....

There are two main related problems here: 1. In order for `Type.createEnum` to work, default values will have to be considered at run-time. This means that the enum constructor functions...

> Just do var x = SomeEnum.SomeConstructor and the default value is lost. You're right, I was somehow thinking that it would turn the type into not having optional arguments,...

Some remarks: ## Metadata targets as return types This is a bit too clever. The main problem I see is that we cannot express the targets of something like `@:final`,...

There's a long-standing tradition that whenever reverse iteration comes up, someone points out the `-->` operator: ``` function main() { var i = 10; while (i --> 0) { trace(i);...

This is a nice idea but is not going to be implemented anytime soon, so we might as well close it now. Let's instead focus on existing architectures/platforms for this.

Let's can this idea for now, I really don't think it's worth the effort.