This problem will probably get fixed soon. To get an idea of things that Nicholas (the language author) is working on, you can keep tabs on this page: http://

This problem will probably get fixed soon. To get an idea of things that Nicholas (the language author) is working on, you can keep tabs on this page: http://haxe.org/com/features http://haxe.org/com/features (e.g. optional structure types) There are still a few kinks in the generics as well, more complex (but common) method signatures won't work, like this one: class GenericMap { static public function map <A, B, C:IFold<A>, D:(ICreateEmpty<B>, IAdd<B>) > ( c : C, f : A -> B ) : D return c.fold( createEmpty(), function(a,d) return d.add(a) ) } The haxe compiler is geared to be very quick, and I'm assuming recursive structural subtyping and complex generics might make things too slow. The compiler is intimately integrated into most haxe workflows... it is used not only for compilation, but it also plays a key role in providing automatic field completions.