An experimental implementation of STARK - #125
Open
mlaveaux wants to merge 48 commits into
Open
Conversation
…tatic expression checks
…n a Result from the evaluation
…he interface similar to the merc_syntax crate.
This file contains hidden or 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.
This should probably not actually be merged into this repository, since it's just using some of the utility crates but rather independent. However, I tried to use Claude to generate an experimental implementation based on the Java code to see if it could be done, and this pull request is just to run the tests. It can parse, typecheck and simulate evolution sequences of STARK specifications, and also perform some basic pertubation checks. The main question is how to verify that the results make sense.