-
Notifications
You must be signed in to change notification settings - Fork 62
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
Better printing of Cryptol errors in saw-remote-api #1130
Conversation
Looks strictly better to me =) |
Upon further inspection, the room for improvement might strictly be a # crypt.py
import os
from pathlib import Path
import cryptol
server = os.environ.get('CRYPTOL_SERVER')
if not server:
server = "cabal new-exec --verbose=0 cryptol-remote-api socket"
print("Running: " + server)
c = cryptol.connect(server)
c.load_module('Cryptol')
print(c.evaluate_expression("1 + True").result())
It looks like |
This improves the output of Cryptol-related errors in `saw-remote-api` slightly, which fixes #1128. There are still some remaining infelicities in how these errors are displayed, but this is a Cryptol-specific problem. The remaining work is being tracked at GaloisInc/cryptol#1106.
I've opened GaloisInc/cryptol#1106 to track improving the Cryptol side of the error message. |
This is a first stab at improving the state of affairs observed in #1128. Before, we had:
Now, we have:
There's obviously some room for improvement still (it still prints a
{'warnings': ... }
dictionary, and the errors lack filenames), but I wanted to submit this now to get @pnwamk's feedback.