-
Notifications
You must be signed in to change notification settings - Fork 3
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
Simple output interface #190
base: main
Are you sure you want to change the base?
Conversation
Use if statements rather than dataclasses or abstract classes
# Conflicts: # atomistics/calculators/ase.py # atomistics/calculators/lammps/calculator.py # atomistics/calculators/lammps/helpers.py # atomistics/calculators/qe.py # atomistics/shared/thermal_expansion.py # atomistics/workflows/elastic/workflow.py # atomistics/workflows/evcurve/workflow.py # atomistics/workflows/phonons/workflow.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This goes back to having strings all over the place, to which I am ideologically opposed.
@samwaseda and I often go back and forth a bunch reviewing PRs trying to convince each other, which is fun and results in some great code improvements. Honestly, here I don't think it's worth your time -- you're unlikely to get me to approve any change introducing this many string checks. If you want to ping others for review I won't be offended, and if there is consensus that this represents an improvement I'll "disagree and commit", but IMO this PR moves backwards.
Use if statements rather than dataclasses or abstract classes