MrChico
MrChico
something should be strict that isn't here
some useful benchmarking scripts can be found at https://github.com/MrChico/evmbench/
Another thing that might help with performance in general is to experiment with `{-## Inline f -##}`. This seems like it can be quite effective, especially when inlining causes specialization...
another thing that can be done here is to unify `mkCodeOps` and `mkOpIx`
There is a workaround: structs are abiencoded as their components, so for example a function: ``` pragma experimental "ABIEncoderV2"; contract A { struct A { uint x; uint y; }...
Another advantage of the nixification approach may be deduplication. Another problem with our current approach that you can have a million folders in the `lib` dir
We could possibly reuse `.dapprc` files locally as a package.json situation. Or just plain json files. Or revive the old Dappfile concept. In practice I feel like 95% pr the...
Very nice, been wanting this for some time. I have fixed ci on master, could you rebase so we can run it again?
wowwww very cool I'm wondering if it might be a good idea to break `dapp mutate gen`, `dapp mutate show-diff` and `dapp mutate filter` into separate files, and then make...
> which doesn't e.g. allow for the generation of a specific number of mutants Not sure if you misunderstood me or not, but to clarify: with `--iterations` I was referring...