Context.signature irregularity.

[Laurence Taylor]

I'm using `Context.signature` to identify anonymous types in the macro context. `signature` produces a different result for a value of typ

[Laurence Taylor]

(sorry)

typedef `AnonType` depending on where the function is called, is that expected behaviour? To clarify, I was calling `signature` in a package 'stx.macro' in a static function, which gives one result, and then as an abstract member method in `stx.macro.clone`, which produced another.

It's kind of confusing.

regards,

Laurence

[Nicolas Cannasse]

Le 01/07/2016 à 11:48, Laurence Taylor a écrit :
> (sorry)
> typedef `AnonType` depending on where the function is called, is that
> expected behaviour? To clarify, I was calling `signature` in a package
> 'stx.macro' in a static function, which gives one result, and then as an
> abstract member method in `stx.macro.clone`, which produced another.
>
> It's kind of confusing.

"Type" might have references that will trigger different values, try on
a ComplexType instead.

Best,
Nicolas

[Laurence Taylor]

OK, thanks

Loz

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
--- You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.