Skip to content
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

Reasoning behind design of annotateWithSystems and execProofMethod #614

Open
felixlinker opened this issue Jan 24, 2024 · 0 comments
Open

Comments

@felixlinker
Copy link
Contributor

felixlinker commented Jan 24, 2024

The function execProofMethod returns Proof () and only annotates the proof steps with the methods solved, but does execute the proof method itself. annotateWithSystems then takes these annotations and saves the resulting system in the proof tree. This causes another call to execProofMethod (here), and I presume, that Haskell is not lazy enough to figure out that these two calls have the same result. See this line.

Does anybody know the reasoning behind this design? Why not let execProofMethod return Proof (Maybe System) immediately?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant