leanprover / leanprover/lean4

RFC: tracking panic freedom

Open
#13,659 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P-medium RFC
Dominant language
Lean
Stars
9.2k
Forks
990
Avg merge
1d 17h
Merged PRs (30d)
175

Description

Proposal

This is a placeholder/collection RFC for tracking use of panics in Lean programs, anywhere from checking mere call graph reachability of panic to proving that a specific execution is panic-free. Please share use cases here that could inform a future implementation of such a feature.

Impact

Add 👍 to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add 👍 to it.

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.

Research direction

Start with the proposal in issue #13659 and review the linked related issues and reactions for use cases. Define the scope of panic tracking, from call-graph reachability to proving a specific execution panic-free; this RFC is complete when a concrete implementation direction is agreed.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.