Skip to content

Conversation

@strub
Copy link
Member

@strub strub commented Jan 26, 2026

No description provided.

@strub strub self-assigned this Jan 26, 2026
only when the program starts with an if, so the proof can split immediately
from the initial state. If the conditional appears deeper in the code,
you must first use the ``seq`` tactic to separate the earlier commands
from the conditional.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could also use a different tactic that gets rid of the earlier statements, such as sp. Maybe that's worth mentioning? If not, then I suggest using "can" rather than "must".

Also, "commands" -> "statements".

@namasikanam
Copy link
Collaborator

I fixed the eHL example and added an explanation. (The explanation is based on the understanding of the meaning of eHL judgment.)

To avoid mixing things up, I use a separate commit for the moment. If my commit okay, I can merge the two commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants