@:forward() for abstracts about dox HOT 8 CLOSED

Nope... I guess in this case you'd want to forward the documentation from the forwarded method.

from dox.

I don't think we output any metadata at the moment, do we?

from dox.

Ah, that didn't occur to me. I'm not sure that's a good idea though because the forwarded documentation might talk about this String and reference methods on the underlying type which are not forwarded to the abstract.

We should treat this just like normal class inheritance I think.

from dox.

I ran into this today and would like a fix. Are there any updates on this issue (from three years ago)? This is really a problem because, in my case (sample gist here) I can't simply write docs on non-existent methods in the non-abstract type.

from dox.

We're having the same issue.

We use abstracts to support OpenGL ES 3.0, OpenGL ES 2.0, WebGL 2 and WebGL contexts. The abstracts use @:forward() to limit the properties and methods that are available (without having to retype them all, there are a lot!)

This page (especially) is disappointing:

http://api.lime.software/lime/graphics/OpenGLES2RenderContext.html

Supporting "Inherited Variables" and "Inherited Methods" would be a reasonable way to handle this probably

from dox.

@Simn @Gama11 is this a Haxe or a dox issue?

from dox.

Dox

from dox.

@Simn I think you can close this issue now.

from dox.