Since dalbit uses a crate full_moon to parse lua files including Lua5.3, the lua53 feature was specified with full_moon.
A dependency full_moon was shared with darklua and features were combined, causing darklua to parse lua53 syntax as well, which caused issues, especially conflicts between luau's generics and syntax and lua53's bit-shifting operators(>> and <<)
I think darklua, like dalbit, can also be solved by specifying the LuaVersion using the full_moon::parse_fallible function.
Would like to see this change probably in 0.2.1
Since dalbit uses a crate
full_moonto parse lua files including Lua5.3, thelua53feature was specified withfull_moon.A dependency
full_moonwas shared with darklua and features were combined, causing darklua to parse lua53 syntax as well, which caused issues, especially conflicts between luau's generics and syntax and lua53's bit-shifting operators(>>and<<)I think darklua, like dalbit, can also be solved by specifying the
LuaVersionusing thefull_moon::parse_falliblefunction.Would like to see this change probably in
0.2.1