-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add --> true
if not present
#57
Comments
I agree with the sentiment, but I can't come up with a good solution where you could still preserve checking that the fact statement is well formed. |
How about first trying the fact statement as is; if it would give the current error, then try adding the |
but then any statement would "work" at compile time, even if it did not make sense. |
Is it possible to call a method towards the end that dispatches on a bool vs anything else:
I admit I haven't looked as to whether this is feasible... just an idea. |
I find myself writing things like
a lot, instead of
Could we add the
--> true
automatically if it is not present, to make it more likeBase.Test
and save effort? Enabling this could be made optional.The text was updated successfully, but these errors were encountered: