rust-lang / rust-lang/rustc-dev-guide
Look through closures meeting
Open
Nobody has claimed this yet.
A-closures
E-help-wanted
E-medium
E-needs-writeup
T-compiler
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
Here is some useful discussion from Niko about type checking closures:
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 by reviewing the linked YouTube discussion and HackMD notes about type checking closures. The issue names no files or tests, and it does not define the intended rustc-dev-guide change, so clarify the target documentation and acceptance criteria before editing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100