Guilherme Dantas
Guilherme Dantas
@scoder I think these are really important changes, could you review it?
> One issue is that it seems to become less clear when exceptions and Python frames (which can hold on to arbitrarily large amounts of data) are getting cleaned up...
> There was a related discussion going on on python-dev, so I asked and there seems to be general interest > in improving the C-API for this. Not something for...
On the contrary, Lua users expect packed arguments to only be unpacked only if they're last, and bringing the Python behavior to Lua calls would be a source of unnecessary...
We can, of course, rename `python.args` to `python.unpack` or something related to give the user a cue for the same Lua semantics as `table.unpack` but for Python arguments.
> Is this impacted by the refcouting changes in #171? No, there is still a reference cycle. Basically, in the example I gave, `d` is holding "hostage" **the** reference to...
The following Lua code should do the trick. The `__newindex` is triggered every new entry. The `__metatable` prevents others from accessing the metatable or overriding it. ```lua setmetatable(_G, {__newindex =...
This feature would be very useful when checking for errors in Forge: ```solidity vm.expectRevert(abi.encodeError(MyContract.MyError, arg1, arg2)); ```
If `stdin` is a bad idea, an option like `--arguments ` would also work.
Just note that I don't know how to program Vim syntax files, so I won't be able to make a PR for this.