-
Notifications
You must be signed in to change notification settings - Fork 100
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
Improvements to requirements #124
Labels
Comments
This is great, and the new requirements functionality is awesome! Can we merge the improvements checklist into the original post to make it easier to track. |
Done. BTW, I personally don't ever expect to get around to doing any of these tasks, haha - it will only happen if someone else gets deeply involved with this. |
Seems like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the requirements system turns out to be useful, the following improvements could be made
@POMDP_require
block, it will not show any@req
s that come after the error. A better way to fail would be to show the requirement (but possibly without all the type information). It is not clear how to handle cases when a@req
is in an if statement or has some other conditionality (difficult)should work in addition to
which already works. (easy)
@req
and@subreq
- do they need to be different? (meidum)The text was updated successfully, but these errors were encountered: