Open kevinresol opened 8 years ago
maybe
Just ran into this myself - I assumed @:forward would carry over the operator overloads by default (same goes for @:to, @:from metas). I guess for now adding to
and from
the base type does the same job?
this would be great for abstracts of numeric types
This is mostly a design question because I'm not sure if @:forward
should pick up additional semantics like that, or if a different metadata should be used instead.
Using the same meta could have unintended side effects for existing code at this point, exposing operators that were not meant to be exposed by the author.
I agree this should be a new meta.
Any news on this?
That would be really great
If I have an abstract over another abstract, the
@:forward
meta won't forward the underlying abstract's operator overloads. Can it be supported?Example: http://try.haxe.org/#eBedf