leanprover / leanprover/TensorLib
Document type promotion if/when we implement it
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 49
- Forks
- 10
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 2
Description
Triton has a nice section on type promotion. We currently only implement explicit casting using .astype. If/when we move to automatic promotion we should document it like the Triton folks. (We don't require manual broadcastTo so I guess we shouldn't require astype.)
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 linked Triton type-promotion section and review TensorLib's current explicit .astype behavior. Confirm whether automatic promotion has been implemented; done means documenting the supported promotion rules and whether users still need astype, including the stated broadcast behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100