rain
New site looks great!
CI failing because I broke `seth --abi-decode` by parenthesising the output on a single line. The current `--abi-decode` is broken though: ``` $ seth --abi-decode "f()(bool[][],uint)" 0x000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000 true,true,true,false 1 ```...
Last year I considered changing the memory stuff to work with LazyByteString, which could help here (?), but it seemed like a lot of work.
Would be nice if the `--version` output both the version number and the commit hash. This would help with 1) easy checkout and 2) disambiguation if I build locally from...
I think `--version` is more expected from other cli tools, so it should at least alias to `version` (e.g. `git` allows both). Also we have `seth --to-wei` etc. as commands...
I've done this in a branch along with a bunch of other abi stuff. Will make a pr soon.
Using this as a library would mean having the cost of DELEGATECALL (700 gas) on every arithmetic operation. Have you considered this? [not necessarily true, see below]
I was incorrect in the above comment about `delegatecall` being used everywhere. This is only true for `public` functions. However the functions in ds-math are all `internal`, so a user...
Maybe there is a better `id` scheme than incrementing? For example, a hash of the caller and a nonce.
No, this is not intentional and there is no relation to the technical terms. We should probably change the wording to avoid confusion. Perhaps drop the terms entirely: ```markdown ####...