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

feature request: go to location when "F*: subprocess exited". #57

Closed
fournet opened this issue Apr 21, 2017 · 1 comment · Fixed by FStarLang/FStar#1266
Closed

feature request: go to location when "F*: subprocess exited". #57

fournet opened this issue Apr 21, 2017 · 1 comment · Fixed by FStarLang/FStar#1266

Comments

@fournet
Copy link

fournet commented Apr 21, 2017

I often make syntax errors. I get F*: subprocess exited on the command line, and go to the Messages buffer to know where to look at:

[F* raw output] Interactive mode; ignoring --verify_module{"kind":"protocol-info","version":1,"features":["autocomplete","describe-protocol","exit","lookup","lookup/documentation","pop","push"]}
[F* error] C:/cygwin64/home/fournet/everest/mitls-fstar/src/tls/Handshake.fst(310,18-310,18): (Error) Syntax error: Parsing.Parse_error
[F* error] 1 error was reported (see above)
F*: subprocess exited.
Mark set [2 times]

Displaying the detailed error within my fstar buffer would be very convenient.

@cpitclaudel
Copy link
Contributor

Yeah, it's a pain. But it would be much better if F* simply didn't die (and instead reported a regular error). See FStarLang/FStar#912 for the F* side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants