doc: notes on tooling: circomkit, circomspect, circomscribe, picus, circom-mutator #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
add notes on usage and context for the following circom analysis tools in readme:
This PR adds notes and demos in the readme on 3 tools worth using.
picusI was unable to build,circomscribeseemed to have no obvious use case, andcircom-mutatorseemed like it would take a day before I understood what was going on. The first and the last could be useful, but seemed too high upfront learning curve to figure out in a day (or get to build at all in the case ofpicus, though Matt says he was able to build it).I'm going to follow this PR up tomorrow with more notes from a few of the resources I mention at the bottom of this readme, which I didn't get to today.