-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to remove keys from hashes after interop #82
Comments
Hey, can you try disable |
looks like that does fix it node << EOF
> new (require("wasmoon").LuaFactory)().createEngine({enableProxy:false}).then(lua => { lua.global.set('identity', x => x); lua.doString("obj=identity({print_me='foobar',dont_print_me='foobar'}); obj.dont_print_me=nil; for k,v in pairs(obj) do print(k); end") });
> EOF
print_me i saw some other issues mentioning these config options, but no documentation describing what they do. is there some somewhere? |
closing because the also, you might consider disabling the proxy by default, because it really causes some issues in otherwise valid LUA code |
No, I'm very bad at documenting (PRs welcome)
Actually I think this issue specifically can be a bug and not a expected behaviour of proxying. I will reopen to check this later. |
in a normal lua environment, my understanding is that the normal way to remove a key from a hash is to set its value to nil, like this:
prints only the one key
in wasmoon it works the same with no interop
prints only the one key
but if i interop at all with js i get both keys
gets both keys
i'm experiencing a bunch of bugs because in normal code you never expect looping over
pairs
to return null values, but with wasmoon it does in this case. is there something i can do to fix this?using
[email protected]
The text was updated successfully, but these errors were encountered: