-
Notifications
You must be signed in to change notification settings - Fork 72
Compiler Feature Backlog Bonanza #484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
meeting scheduled for 2022-03-04 |
followup meeting scheduled for 2022-03-18 |
another backlog bonanza is scheduled for 2022-06-24 |
Here's the meeting doc that drove these meetings, here's that: https://hackmd.io/h_tyzNEKS_Kc2OY_rSm28g Here's the full list of feature backlog bonanzas, with links to the zulip chats: |
I suspect this should stay open until we've finished going through the issues starting from here: https://hackmd.io/h_tyzNEKS_Kc2OY_rSm28g#Tracking-Issues-input-queue |
Meeting scheduled for March, 7th, 10 a.m. (TZ: -05) as per compiler meeting. @pnkfelix it's been quite some time since you filed this proposal, do you think you can be there too? It's probably ok if you don't, given we scheduled this after years. Also, I wonder who else could interested in participating. @rustbot label meeting-scheduled |
Meeting proposal info
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-rustdocUPDATE: new query filtering all C-tracking issues without a team assigned.
UPDATE: new query filtering C-tracking issues filtering where 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).
The text was updated successfully, but these errors were encountered: