-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting notes #47
Comments
2021-02-09Completed
Issues:Memory problemSemantics can't build, require too much time an memory. Likely due to configuration compostions. Actions:
DiscussionWhat are next steps? What would be cool tools. Everyone agree that symbolic execution, verification, and automatic test case generation would all be great. They are long-term, though. Andrei suggested we should plug ElrondWasm into their regular CI when it's done, to test Arwen against the K semantics. We could also make the Elrond semantics a more complete documentation document, like the jello paper. Once we can generate a report for the Multisig contract we will give that to @virgil-serbanuta and other devs on the Elrond side for feedback and ideas on how it should become more useful. Right now, the default approach is:
|
2021-02-23Done this week
DiscussionFocus now: finish the semantics/clean up, be able to run basic tests, produce reports. Update the elrond-wasm-rs dependency. Next step: investigate source mapping. What can we do, how well do existing source mapping tools work for our purposes. |
No description provided.
The text was updated successfully, but these errors were encountered: