Abstract syntax tree parser for ConfigSpace#413
Open
thijssnelleman wants to merge 9 commits intomainfrom
Open
Conversation
Collaborator
Author
|
TODO: Add more docs into the methods, s.t. we have examples for the documentation site |
Collaborator
Author
|
Added new docs example for usage, cleaned up code and other comments. I think its ready for a review now. |
Collaborator
Author
|
@mfeurer Reminder for this PR |
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
1 participant
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.
Adding in logic for parsing expressions into ConfigSpace Conditions/Forbiddens. This is aimed to take general logic expressions (strings) and uses the AST library to convert it into a ConfigSpace expression.
The reason of this being necessary is as a build up towards enabling parsing a ConfigSpace from other notation files, such as PCS files from SMAC2, IRACE etc.