-
Notifications
You must be signed in to change notification settings - Fork 80
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
assumption?
#281
base: master
Are you sure you want to change the base?
assumption?
#281
Conversation
@@ -0,0 +1,3 @@ | |||
{"msgs":[{"caption":"trace output","file_name":"assumption.lean","pos_col":2,"pos_line":3,"severity":"information","text":"Try this: h1\n"}],"response":"all_messages"} |
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.
this file is actually garbage, I don't know how to get the output of the test
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.
cd tests/lean
./test_single.sh ../../bin/lean assumption.lean
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.
The output is still wrong. Please fix it until the command above prints -- checked
.
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.
hmm actually I still don't know how to build bin/lean
in the first place
probably it's these instructions
https://github.com/leanprover-community/lean/blob/master/doc/make/index.md#generic-build-instructions
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.
Yes, where are you stuck?
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.
now I'm just waiting on the build. before I was stuck on understanding the error messages that came out of ./test_single.sh ../../bin/lean assumption.lean
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.
Now I have a real lean binary. I'm getting "error: unexpected token" at the question mark. Most of my debugging strategies rely on VSCode; is there a way to tell it to use the local lean binary?
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.
Hmm. Seems like the current commit gives lots of errors like this. I thought the approach using the optional parse argument would prevent these. I think I should give up.
/Users/jstark/lean-projects/lean/library/init/meta/interactive.lean:1057:30: error: type mismatch at application
try assumption
term
assumption
has type
parse (tk "?")? → tactic unit
but is expected to have type
itactic
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 think you should just replace these references to assumption
by tactic.assumption
. The ?
parser only works when the tactic is parsed in an begin ... end
block (or by ...
).
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.
Okay, I think I have implemented that suggestion in the latest commit. I'm still getting the following, which seems to be the opposite problem (i want it to use the version with the parser and it uses the version without) I tried adding import tactic.interactive
but i could not resolve that import.
/Users/jstark/lean-projects/lean/tests/lean/assumption.lean:3:12: error: unexpected token
/Users/jstark/lean-projects/lean/tests/lean/assumption.lean:4:0: error: invalid 'end', there is no open namespace/section
I feel obligated to mention that you could also implement |
Co-authored-by: Yury G. Kudryashov <[email protected]>
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
I think for the precedence `?`:max You should also add an |
There's currently an |
If you write There are two tests that use |
so these tests need |
in the latest commit, I have but the |
I think you should add an bors try |
tryBuild failed: |
Oh wow, the precedence change broke a lot of stuff. You should post a message on Zulip about this. I'm not sure what the correct solution here is. |
Maybe this approach would get around the current problem. Note that |
See this topic and this topic on zulip.