Coq backend - Githubissues

Armael commented 5 years ago

Remaining:

[x] write an opam file for the grader
[x] write a "prepare.sh" script that sets up a local opam switch with coq+the grader
[x] port the grader to serapi v8.10 (coq v8.9 contains at least one known soundness bug, we should use a possibly hardened version of coq 8.10)
[x] finish the poller.py script to make it actually call the grader

Questions wrt the grader<->poller plumbing: how is partial success handled again? As far as I can tell, at the moment the poller script can only answer (yes/no) + some text message. If the text message gets parsed afterwards, what is the format exactly? Also, how does this interact with allow_sorry?

wimmers commented 5 years ago

Yes, so you are right. It simply is a text message. For Isabelle, it contains a JSON that gives a mapping from 'tasks' to 'points'. We should discuss and fix that format. The obvious thing would probably be to use a free-form JSON that is parsed in a proof-assistant specific way in the frontend. However, it is probably not a good idea to introduce too much proof-assistant specific code in the frontend.

Armael commented 5 years ago

Merging, I think this is more or less ready now :).

isabelle-prover / proving-contest-backends

Coq backend #2