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

Cryptol Model: Replace magic constants with variables #69

Open
abakst opened this issue Jan 19, 2022 · 1 comment
Open

Cryptol Model: Replace magic constants with variables #69

abakst opened this issue Jan 19, 2022 · 1 comment
Labels
cryptol Issues related to our Cryptol specifications, or use thereof. ENHANCEMENT New feature or request Someday Issues that are not required by our current contract, but we'd like to attend to someday.
Milestone
Second Polishing ...

Comments

@abakst
Copy link
Contributor

abakst commented Jan 19, 2022

Due to a limitation in crymp, we have all sorts of references to magic constants (e.g. sensors @ 0 instead of sensors @ T). However, toplevels like

T : [2]
T = 2

seem to be problematic for crymp. We should track the issue and fix when possible.
@abakst abakst added ENHANCEMENT New feature or request cryptol Issues related to our Cryptol specifications, or use thereof. labels Jan 19, 2022
@abakst abakst mentioned this issue Jan 26, 2022
Merged
@kiniry
Copy link
Member

kiniry commented Apr 18, 2022

Should this be a Someday issue, as we aren't going to fix crymp during the execution of HARDENS? I'll put it there for now.

@kiniry kiniry added the Someday Issues that are not required by our current contract, but we'd like to attend to someday. label Apr 18, 2022
@kiniry kiniry added this to the Second Polishing Release milestone May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cryptol Issues related to our Cryptol specifications, or use thereof. ENHANCEMENT New feature or request Someday Issues that are not required by our current contract, but we'd like to attend to someday.
Projects
None yet
Milestone
Second Polishing Release
Development

No branches or pull requests
2 participants
@abakst @kiniry