rust-lang / rust-lang/compiler-team
Compiler Feature Backlog Bonanza
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 433
- Forks
- 73
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Meeting proposal info
- Title: Compiler Feature Backlog Bonanza
- Type: technical
Summary
We're going to review the backlog of unimplemented or partially implemented compiler features.
Consider e.g. this github query: https://github.com/rust-lang/rust/issues?page=2&q=is%3Aopen+is%3Aissue+label%3AC-tracking-issue+-label%3AT-libs-api+-label%3AT-libs+-label%3AT-lang+-label%3AT-rustdoc
UPDATE: new query filtering all C-tracking issues without a team assigned.
UPDATE: new query filtering C-tracking issues filtering where only T-compiler is tagged.
Before the meeting, Felix/Wesley will make a doc that we can fill in with notes on the various statuses. (It might be cool to leverage Github Projects too, see e.g. T-lang's initiatives.)
The list of meeting about this topic is kept updated at this comment.
About this issue
This issue corresponds to a meeting proposal for the compiler team
steering meeting. It corresponds to a possible topic of
discussion. You can read more about the steering meeting procedure
here.
Comment policy
These issues are meant to be used as an "announcements channel"
regarding the proposal, and not as a place to discuss the technical
details. Feel free to subscribe to updates. We'll post comments when
reviewing the proposal in meetings or making a scheduling decision.
In the meantime, if you have questions or ideas, ping the proposers
on Zulip (or elsewhere).
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 compiler tracking-issue queries and the meeting-list comment linked in this issue, then read the steering meeting procedure. The proposal is complete when the backlog review is scheduled and its status notes are captured in the planned document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100