Lightning-AI / Lightning-AI/lightning-thunder
remove thunder.trace as an entry point
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
(and then also remove the handling of absent compile options)
See
https://github.com/Lightning-AI/lightning-thunder/pull/1423#discussion_r1840389395
Contributor guide
No contributing guide indexed for this repository
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 with the discussion linked from PR #1423, especially the referenced review comment, to understand why thunder.trace and absent compile options should be removed. Locate the entry-point and compile-option handling in the repository, then verify that both behaviors are removed without breaking existing compiler usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100