You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 20, 2021. It is now read-only.
As I'm getting closer to being able to output k specs from act2, I'm thinking about how to integrate it to the klab workflow. Roughly, we want to replace klab build with act compile, and there is some experimentation going on on the act2 branch of this repo.
In this process, I expect the following things to change:
I'm not convinced having the calls section as part of the behaviour is a good idea. I think better would be to simply indicate the dependencies of specs in the config.json for each directory, to get the gas extraction and proving workflow from that.
Obviously, there are syntactic changes to how specs are written, which in general will make many specs a lot shorter.
Instead of a separate storage markdown file, the new act format works with a spec for the constructor. From this both storage locations and type checking can be inferred.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As I'm getting closer to being able to output k specs from act2, I'm thinking about how to integrate it to the klab workflow. Roughly, we want to replace
klab build
withact compile
, and there is some experimentation going on on the act2 branch of this repo.In this process, I expect the following things to change:
calls
section as part of the behaviour is a good idea. I think better would be to simply indicate the dependencies of specs in theconfig.json
for each directory, to get the gas extraction and proving workflow from that.storage
markdown file, the new act format works with a spec for the constructor. From this both storage locations and type checking can be inferred.The text was updated successfully, but these errors were encountered: