Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

[java] @:overload on different types of functions should not be allowed #2689

singpolyma opened this Issue Feb 28, 2014 · 2 comments


None yet
3 participants

singpolyma commented Feb 28, 2014

If I use @:overload to have multiple methods that take different types of functions, haxe allows it, but generates methods on the java side that all take arguments of the unparameterised type Function -- so javac complains.


waneck commented Feb 28, 2014

@:overload's primary goal is to provide a consistent way to interact with pure Java/C# code. Using it for user code - like the case with Haxe functions is not portable between the other targets, and may cause conflicts like this one.
I'll leave this issue open since we could use an error on the haxe side, instead of failing on the Java compiler


singpolyma commented Feb 28, 2014

@waneck Yeah, an error on the haxe side is what I was thinking would be good.

@waneck waneck self-assigned this Mar 1, 2014

@ncannasse ncannasse added this to the 3.2 milestone Mar 4, 2014

@waneck waneck modified the milestones: Long term, 3.2 Sep 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment