Support translating struct updates to Bluespec. Refs #10. #13
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.
To accomplish this, we leverage Bluespec's functional struct updates. For instance, suppose we have a Copilot struct with fields
x :: Field "x" Int32
andy :: Field "y" Int32
. If we update a struct'sx
field to be42
, then the generated Bluespec code would look roughly likev { x = 42 }
.In order to test
UpdateField
(thecopilot-core
representation of struct field updates), we also generalize the test suite infrastructure a bit, as we need to be able to display and read struct values. Thankfully, this proves relatively straightforward.Fixes #10.