-
Notifications
You must be signed in to change notification settings - Fork 88
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
DRY m_checker #591
Comments
I don't mind doing it. It will take a while though - there are so many checkers! |
True. Well you don't have to do it all in one day, up to you. |
In fact, if you do all of the ones in one of the sub-codes (preprocess, sim., or postprocess), I will merge the PRs one-at-a-time. |
Okay! I'll give it a try |
May I know if this is all right or there's a better way?:
outputs
|
Also stuff like this are giving me issues:
Should I keep it as it is and not change it to @:PROHIBIT? |
what is the challenge in changing this to prohibit? |
w
It seems like maybe this should be an |
Maybe the first part of the "Prohibited condition: ..." message isn't as helpful as the custom message? But yeah it still works (just a bit long):
from the code:
|
It seems like the code you wrote is nicer than what we had before, though you might want to introduce a line break? (assuming this is allowed in macros). |
Yes line breaks work in macros and I'll add them. I'll change everything to PROHIBIT then |
I'm open to other ideas. Or you can concoct something with @henryleberre and bounce it off me. |
Yeah I'm sure Henry will have better ideas, and I'm happy to improve the code further. Right now I'm submitting what I have as a PR draft and maybe you could check out the result and see if you like it. |
From #544 (comment):
The text was updated successfully, but these errors were encountered: