[Cider 2.0] Basic Simulation flow #1912
Merged
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
rachitnigam
pushed a commit
that referenced
this pull request
Feb 16, 2024
* clippy lint * debug printing * misc nonsense * checkpoint * add run program * rename the stdmem impls * move the get_next for control points into two separate non-internal functions * some light documentation and renaming * add an assert * add some dinky placeholder printing for internal state * fix some issues with the memories and move serialization * set the go ports appropriately * clean up warnings
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 adds enough of the infrastructure to allow some programs to simulate on the flattened version of Cider. This is missing a bunch of things, including a proper way of presenting output but is a good starting point. I also moved a few things around to make life easier in the future, mainly making the serialization logic used for memories exist largely in its own module.