leanprover-community / leanprover-community/lean
trace import
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 434
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
From: https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/Lean.203.2E7/near/189816815
Sebastian says:
Btw, you might be interested in something like the trace.import trace class I added to Lean 4 before removing that file altogether: https://github.com/leanprover/lean4/commit/75b2b09c08be9206732bc7a9934c7c18b5f094b2
Also https://github.com/leanprover/lean4/commit/15d11cc48362330f6e90791a2101444798734e21
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the two Lean 4 commits linked in the issue and the referenced Zulip discussion. The issue does not define the desired scope or completion criteria, so clarify what trace.import should provide before identifying the relevant Lean compiler entry points and tests.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100