Add interfaces to contract files and Jupyter Labs demo #18
Conversation
|
When you have leisure time, I've posted the draft pull request here #18 The only questions I had was the convention for where to store Vyper interfaces — from researching it looked like it was most common to keep these in the contract file (they handled struct datatypes better this way too), but I can break these out easily into a separate file or multiple files if preferred. It was also not clear how Vyper interfaces are best meant to handle function polymorphism (overloading of functions), so I only included the version of the functions with the most arguments (ie without optional parameters). |
|
Uhm... I think, Vyper folks usually have no problem with interfaces - I meant .sol ones. Apparently @iamdefinitelyahuman has a tool to autogenerate those https://github.com/iamdefinitelyahuman/abi2solc though, so just the matter of properly communicating it to devs |
No description provided.