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

Forcing reload of already-imported Cryptol files #112

Open
brianhuffman opened this issue Mar 9, 2016 · 1 comment
Open

Forcing reload of already-imported Cryptol files #112

brianhuffman opened this issue Mar 9, 2016 · 1 comment
Labels
better-in-python Will be fixed by switching to python frontend needs test Issues for which we should add a regression test type: enhancement Issues describing an improvement to an existing feature or capability usability An issue that impedes efficient understanding and use
Milestone

Comments

@brianhuffman
Copy link
Contributor

If we load a .cry file in saw-script with "import", and then modify the .cry file, there is currently no way to force saw-script to reload the modified source file (short of quitting and restarting saw). Entering another "import" command does nothing if saw-script has already loaded the named file.

We need a way to clear the set of imported cryptol modules from the REPL, so that we can reimport them again.

@brianhuffman brianhuffman self-assigned this Aug 5, 2016
@atomb atomb added the type: enhancement Issues describing an improvement to an existing feature or capability label May 2, 2017
@atomb atomb added this to the 1.0 milestone Jun 4, 2019
@atomb atomb modified the milestones: 1.0, 0.4 Oct 1, 2019
@atomb atomb modified the milestones: 0.4, 1.0 Oct 18, 2019
@atomb atomb modified the milestones: 0.5, 0.6 Apr 16, 2020
@atomb atomb added the usability An issue that impedes efficient understanding and use label Apr 28, 2020
@atomb atomb modified the milestones: 0.6, 0.7 Aug 31, 2020
@brianhuffman
Copy link
Contributor Author

Unassigning myself, as I don't plan to work on this anytime soon.

@brianhuffman brianhuffman removed their assignment Dec 4, 2020
@atomb atomb modified the milestones: 0.7, 0.8 Dec 14, 2020
@atomb atomb added the better-in-python Will be fixed by switching to python frontend label Apr 9, 2021
@atomb atomb removed this from the 0.8 milestone Apr 9, 2021
brianhuffman pushed a commit that referenced this issue Apr 26, 2021
Make ruleOfProp return a `Maybe` instead of calling `error`.
@sauclovian-g sauclovian-g added this to the 2025T1 milestone Oct 29, 2024
@sauclovian-g sauclovian-g added the needs test Issues for which we should add a regression test label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
better-in-python Will be fixed by switching to python frontend needs test Issues for which we should add a regression test type: enhancement Issues describing an improvement to an existing feature or capability usability An issue that impedes efficient understanding and use
Projects
None yet
Development

No branches or pull requests

4 participants
@atomb @brianhuffman @sauclovian-g and others