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

Allow pausing of cache replay for a specific proof #3351

Closed
unp1 opened this issue Nov 14, 2023 · 1 comment
Closed

Allow pausing of cache replay for a specific proof #3351

unp1 opened this issue Nov 14, 2023 · 1 comment
Assignees
Labels
Feature New feature or request GUI
Milestone

Comments

@unp1
Copy link
Member

unp1 commented Nov 14, 2023

Please describe your proposal in a ONE sentence

One sentence describing your idea

Allow to pause proof cache replay for a single proof (without needing to switch it off globally)

Underlying problem

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Sometimes (e.g., teaching) one wants to perform the same proof using different alternatives (inlining, contract, manual steps etc.) or simple debugging. In that case proof cache replay means it too well :-)

Usage Scenario

Who (user scenario) would benefit from implementing the idea?
Describe a short use case scenario in which the suggested idea is featured.
Describe the solution you'd like: A clear and concise description of what you want to happen.

I would like to be able to (for example) right-click on the proof caching information in the status line and to pause the caching for the moment and later to resume it.

Alternatives

A clear and concise description of any alternative solutions or features you've considered.
Why is the suggestion the best alternative?

The alternative would be to switch the feature off globally, which is more cumbersome for the few times one wants to switch it off, as in general one really wants caching.

Estimated effort

If you can: Estimate the effort that has to be invested to implement the feature request.
Is there still discussion needed? Or is it purely implementation? Expertises needed?

Additional context

Add any other context or screenshots about the feature request here.

@unp1 unp1 added GUI Prover Core Feature New feature or request labels Nov 14, 2023
@FliegendeWurst FliegendeWurst self-assigned this Nov 14, 2023
@FliegendeWurst FliegendeWurst added this to the v2.14.0 milestone Nov 14, 2023
@Drodt Drodt added the HacKeYthon Candidate Issue for HacKeYthon '24 label Jan 18, 2024
@wadoon wadoon removed the HacKeYthon Candidate Issue for HacKeYthon '24 label Jan 26, 2024
@WolframPfeifer
Copy link
Member

Closed by #3305.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature or request GUI
Projects
None yet
Development

No branches or pull requests

5 participants