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
All the reference fixtures in JSON format show some properties as having null values. Lua of course handles nil a bit differently than some languages. For the purposes of comparing fixtures when I load the JSON into a Lua table everything works out fine because the nulls load as nils and the comparison works okay. However trying to get JSON output that matches is a bit more difficult. For external comparison I'm currently stripping the null's usig jq:
Should we be using a custom null value in our AST internally so we can match what other implementations have? Or is Lua's nil handling going to suffice?
The text was updated successfully, but these errors were encountered:
alerque
changed the title
Much ado about nothing
Much ado about nothing, aka nilSep 23, 2019
All the reference fixtures in JSON format show some properties as having
null
values. Lua of course handlesnil
a bit differently than some languages. For the purposes of comparing fixtures when I load the JSON into a Lua table everything works out fine because thenull
s load asnil
s and the comparison works okay. However trying to get JSON output that matches is a bit more difficult. For external comparison I'm currently stripping the null's usigjq
:...but that's a hack.
Should we be using a custom
null
value in our AST internally so we can match what other implementations have? Or is Lua'snil
handling going to suffice?The text was updated successfully, but these errors were encountered: