El De-dog-lo

A few comments: 1. I think the fields should be properties and not types e.g. `foo_wizard.factory` and `foo_wizard.interface` 2. `foo_wizard.factory` sounds a bit domain specific. Wonder if something like `foo_wizard.create(*args)`...

> re. the `@factory` decorator -- i think it's actually not necessary for the type checker. ~we do need~ maybe instead we can just introduce a new mode for the...

So, you can't import types from other Vyper contracts. What the docs mean by "regular vyper syntax" is that your file structure and internals should look like this: `interfaces/IFace.vy`: ```vyper...

There's also a longer term fix with libraries that is coming in https://github.com/vyperlang/vyper/issues/2431

This proposal is pretty unclear in it's current format. Is it a set of `MyStruct` objects stored? Just one? What is the size of the type stored in storage? how...

> i guess one open question is, do we assign from the proof or the witness? > ```vyper > # only allowed if a proof is allowed in calldata; bytes...

Note: we should do the same with Event logs

> I like the idea of using the kwargs syntax, not so excited about default values and positional args (both increase the risk of misleading code IMO). To be clear,...

> Here's an idea though, what if we allow "positional" args but only if the variable name is exactly the same as the parameter name. Yes! This is exactly what...

Meeting: only do kwargs