Charles Cooper

> ``` > (venv) custom[feat/archives*] % vyper test4.vy > Error compiling: test4.vy > vyper.exceptions.ModuleNotFound: ethereum.ercs.erc20 > > contract "test4.vy:3", line 3:0 > 2 > ---> 3 from ethereum.ercs import erc20...

> Also, given the number of bugs & minimal client usage, should we hide this feature behind some experimental flag or even deprecate it? no -- it's already a bit...

this improves codesize between 0.5%-1% on some test contracts i have

we should get the venom optimizer to feature parity with the IRnode optimizer, so we can disable the IRnode optimizer without any performance regressions

i'm actually removing the `-p` option for json input in https://github.com/vyperlang/vyper/pull/3891, there will be a `search_paths` option though

closing since #3891 gets rid of the `-p` option for standard json input

this is a dup of https://github.com/vyperlang/vyper/pull/3546 no?

i'd say if we're going to issue a warning, we might as well issue an error. initializing a stateless module seems like an error tbh. (i think in most languages...

i'm not sure yet if this is a compiler bug or docs issue, but i'm leaning towards docs issue. note that this behavior was introduced in https://github.com/vyperlang/vyper/pull/3669, and that this...

this is looking better. i'm still hesitant though, because i tried this myself and realized that the approach doesn't work for `raw_call` -- `raw_call` requires a call site in order...