You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both of these result in EConst(CString($j)) as the expression for i, which means you can't tell them apart. In haxeparser 3.2.0, the escaped $ would actually show as two dollar signs in the expression: EConst(CString($$j))
There's still some failing tests (see #262 and HaxeCheckstyle/haxeparser#36), but I think it's better to ignore those for now than to not test against latest Haxe and haxeparser at all.
I'll go ahead and close this because it's consistent with how Haxe lexes it. I'm not saying that approach isn't shit, but for now I want to keep haxeparser as close to Haxe as possible.
File.hx
(escaped$
):File.hx
(interpolation$
):Both of these result in
EConst(CString($j))
as the expression fori
, which means you can't tell them apart. In haxeparser 3.2.0, the escaped$
would actually show as two dollar signs in the expression:EConst(CString($$j))
This causes some of the failures in HaxeCheckstyle/haxe-checkstyle#262.
The text was updated successfully, but these errors were encountered: