Following up from the call earlier, here's our highest priority request before we launch into phase 1 of the compiler audit next week. Could someone go through the Python AST and/or vyper/ast.py and write down where there's a difference between the Python grammar/semantics and Vyper's? A couple quick examples of what we're thinking about:
structs and contracts into classes and keeps track of the original token outside of the AST (I think).for loops have an else in Python, but Vyper seems to just ignore that. Should it be rejected? Or should it be used?uint256(wei). That probably looks like a function call in the Python AST?Incomplete is okay here... it will just save us a lot of time if we have some pointers to where the interesting bits are.
ast.py works as a filter to catch the parts of python we don't implement. So to handle that we just remove orelse from the For class.ast.py with VyperNode I had to scrape python's ast classes - I could find that script and then we could do a diff and document off of that.GlobalContext._custom_units .units defines the global notion that the units may be used.
blah to the event)