fix current_dir() call when using wasm generation 2: continue_recursive_circuit
#42
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.
Issue #37 details how
create_recursive_circuitcallscurrent_dir(). This was fixed forcreate_recursive_circuitbut notcontinue_recursive_circuit. This PR makes minimal changes to the wasm targetedcontinue_recursive_circuitto remove fs operations as was done in #37.I don't think there is a wasm test suite so I haven't run anything in this repository specifically, but I have confirmed the intended functionality is achieved with this PR in an external repository
edit: need to fix the ci