fix/Fixed fuzz test generation with init-if-needed Anchor feature #131
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.
When using
init-if-neededAnchor feature, the fuzz test generation failed, because we are using Anchor's parsing method to parse the context structs where also the Anchor constraints are parsed and it is verified, that theinit-if-neededfeature is activated properly. However Trdelnik did not activate this feature and the verification during parsing failed.Also this PR resolves the
warning: some crates are on edition 2021 which defaults toresolver = "2", but virtual workspaces default toresolver = "1"``. The resolver is now explicitly set to 1, because it merges the activated features for the whole workspace which is required for theinit-if-neededfeature to be propagated. Note that this warning may still be present due to Anchor settings, but this cannot be influenced by Trdelnik.I have also deactivated some features that were only slowing the compilation but were not necessary for the project to compile.