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.

Sign up for GitHub

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

Jump to bottom

Strictness of trace in reference #426

Closed
yav opened this issue Jun 16, 2017 · 1 comment
Closed

Strictness of trace in reference #426

yav opened this issue Jun 16, 2017 · 1 comment
Assignees
@brianhuffman @robdockins
Labels
maybe-fixed Might be resolved, but this needs to be confirmed. semantics Issues related to the dynamic semantics of Cryptol.
Milestone
2.11.0

Comments

@yav
Copy link
Member

yav commented Jun 16, 2017

User @msaaltink reported a difference in the strictness behavior of trace between the standard and reference interpreter: reference ignores the things that are to be printed, so it is more lazy.

This was done in a comment to another ticket, so I am making this new ticket so we can remember the issue.
@brianhuffman brianhuffman self-assigned this Jul 10, 2018
@brianhuffman brianhuffman added the semantics Issues related to the dynamic semantics of Cryptol. label Jun 21, 2019
@brianhuffman brianhuffman added the maybe-fixed Might be resolved, but this needs to be confirmed. label Jan 29, 2021
@atomb atomb added this to the 2.11.0 milestone Jan 29, 2021
@robdockins robdockins self-assigned this Feb 10, 2021
@robdockins
Copy link
Contributor

I believe this was fixed in 7139ab9

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

@brianhuffman brianhuffman

@robdockins robdockins

Labels
maybe-fixed Might be resolved, but this needs to be confirmed. semantics Issues related to the dynamic semantics of Cryptol.
Projects
None yet
Milestone
2.11.0
Development

No branches or pull requests
4 participants
@yav @atomb @brianhuffman @robdockins