Error handling subsystem for `ktool` module

Open
#4,174 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reading the discussion linked in the issue, especially the proposal to extract KToolError and KompileError. Map the places that call K binaries and define what uniform exception handling and dedicated error output should cover; the work is done when those calls use the agreed exception stack consistently.

Written by the indexing model from the issue text.

Description

pyk

We have several places where we call direct K binaries and such, and would like uniform error handling for them all. Part of that would be to define our own exception stack, with it's own way of printing out issues that happen.

Details here: https://github.com/runtimeverification/pyk/pull/1012#discussion_r1537863131.

Basically, pull out KToolError, and KompileError, and throw those as specific exceptions that we can have dedicated error handling for.

Dominant language
Python
Stars
591
Forks
163
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from runtimeverification/k

All issues in runtimeverification/k

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.