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
Subclass Assumptions Predicate from FOL #1
base: FOL
Are you sure you want to change the base?
Conversation
sd-biswas
commented
Sep 19, 2014
- Subclass assumptions.Predicate from FOL.Callable and rename it to AssumptionsPredicate.
- Subclass assumptions.AppliedPredicate from FOL.Applied and rename it to AppliedAssumptionsPredicate.
- Rename Function and AppliedFunction in FOL.
Can you enable Travis CI on you fork so that the tests run here? |
|
I want you to enable Travis so I can see what is going wrong. |
|
||
class Predicate(Boolean): | ||
class AssumptionsPredicate(Callable): |
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.
I thought your class was called Predicate
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.
It is called Predicate
. But the logic behind Predicate
is in Callable
and similarly logic behind AppliedPredicate
is in Applied
. FOL Predicate
subclasses Callable
and overrides the apply()
method. Subclassing Predicate will produce the exact same result. So it is simply a question of preference.
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.
I would subclass Predicate. That seems clearer, and assumedly its apply would be useful here.
Yeah, I did. But I think it will probably start running after I make a commit (I'll dummy one now and later rebase it out). |
This looks like it is the right idea. |