Bulby
Bulby
This is all confusing, this is my first proposal so bear with me. What I want is java like overloading support, for all target langs, either by using their built...
The third one is impossible to error at compile time because it's dynamic correct? If so, then failing at runtime is probably the only solution, or using the `getProperty` reflection...
So would the adapter function be the "correct" name? ```hx // from child extending Parent override overload function test(i:String) // from parent function test(i:T) ``` would become ```hx // child...
I don't like the idea of runtime type switching though.
It probably would make sense to always keep an adapter function on every class to support dynamic dispatch. However it would still probably be optimal to rename any function we...
I think we should ditch the lowercasing. That just makes it easier to make mistakes, and it allows stuff like ```hx overload function test(i:TestClass) overload function test(i:Testclass) ``` to become...
That makes me think, how would overriding an overloaded function work? ```hx class Parent { overload function test(i:String) overload function test(i:Int) } class Child extends Parent { override overload function...
Yes, I just made a case for this.
I feel like technically this could be done with macros but it'd be a really janky, messy code solution.
I'll update the proposal tommorow to cover these edge cases.