-
Notifications
You must be signed in to change notification settings - Fork 16
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
Support for get-assignment
#216
Comments
So, the current situation, is that the response to the In this very particular instance, where the There are thus two solutions: 1) as said above, try and check I won't have much time to work on that unfortunately, so I can do option 2 (but I don't know when), and if you want/need optin 1), you'll probably need to open a PR. |
I opened this issue mostly for tracking purposes, I don't need a fix for it currently. Long term I think option 2 is acceptable; it would remove the ambiguity/surprises (especially since dolmen does writes warning for invalid models but does not seem to produce any output for valid models). Option 1 would be useful but I don't see myself implementing it in the near future either. |
Dolmen accepts the following files
ga.smt2
andga.rsmt2
without complaining:with
$ dolmen ga.smt2 -r ga.rsmt2 --check-model true $
This is surprising because the assignment is incorrect:
not_p
is defined as(not p)
and can't betrue
whenp
istrue
. However Dolmen clearly knows some stuff aboutnot_p
because if I use the following forga.rsmt2
:I get the following error:
Either correctly parsing
(get-assignment)
or having an error/warning that it is not supported would be less confusing.The text was updated successfully, but these errors were encountered: