-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make cleaner separation between parser and main. #665
Comments
Yes, makes perfect sense. |
Before merging though (or after for that matter), I am wondering if I need to make an adjustment here. The problem I am realizing I will be faced with is that as soon as sub-class Input, using the parser will be unavailable. A better solution, I think, is to initialize Input in Sounds good? |
What would be the need behind inheriting from |
I subclass the C++ classes in Python to add lots of extra Python features which is a lot more difficult to do from pure C++. |
I have no problem to use another approach and maybe you can sketch that in a separate PR, but I fear that you won't be able to create an |
Currently the main interface creates CLArgs to parser arguments, which (depending on input) get passed down into the vroom machinery.
For the most part this is done cleanly in such a way that you don't need CLArgs to use any machinery, with input parser being the only exception.
I propose we make the interface cleaner by keeping CLArgs contain to the main file and just passing it's attribute along explicitly.
The text was updated successfully, but these errors were encountered: