You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A | harpoonaffecting the Harpoon interactive proverB | bugunexpected or incorrect behaviourB | refactorchanging the implementation of existing featuresP | lowlow priority issue
The --stop option was added to Harpoon to assist in debugging command transcripts, to make Harpoon exit on the first command that produces an exception. The problem is that errors that are generated by Harpoon rather than by Beluga do not generate exceptions. They just print an error message.
This is tagged refactor because one should rethink the way exceptions are handled in Harpoon. Perhaps a simple approach is to make all errors proper OCaml exceptions. Since these exceptions have no need to be caught and analyzed, we can just wrap a function of type formatter -> unit -> unit that prints the error message.
The text was updated successfully, but these errors were encountered:
A | harpoonaffecting the Harpoon interactive proverB | bugunexpected or incorrect behaviourB | refactorchanging the implementation of existing featuresP | lowlow priority issue
The
--stop
option was added to Harpoon to assist in debugging command transcripts, to make Harpoon exit on the first command that produces an exception. The problem is that errors that are generated by Harpoon rather than by Beluga do not generate exceptions. They just print an error message.This is tagged
refactor
because one should rethink the way exceptions are handled in Harpoon. Perhaps a simple approach is to make all errors proper OCaml exceptions. Since these exceptions have no need to be caught and analyzed, we can just wrap a function of typeformatter -> unit -> unit
that prints the error message.The text was updated successfully, but these errors were encountered: