List view
Typecheck issues to take care of before 16.1 releases. Expect this milestone to be split into smaller ones
Due by April 1, 2026•15/21 issues closedhttps://github.com/rust-lang/rust/pull/53851/files
No due date- Implement specializable trait types - Same for specializable trait const items - Same for specializable trait functions - Move `is_default` field from `AST::Function` to trait item base class - `#[rustc_specialization_trait]` - `#[rustc_unsafe_specialization_marker]`
No due date- gcc-15/changes.html - news file?
Overdue by 2 month(s)•Due by April 1, 2025Improvements to the `let-else` milestone to improve handling of invalid code
No due date•0/2 issues closed- No due date•0/1 issues closed
- No due date•2/3 issues closed
Continuation of the work done in https://github.com/Rust-GCC/gccrs/milestone/46, in order to implement the last few bits required for a full support of inline assembly.
No due date•1/3 issues closed- Due by September 15, 2025
- Due by July 28, 2025
Handling the issues reported by the rustc testsuite adaptor GSoC 2024 project
Due by September 15, 2025- Due by July 7, 2025
- Overdue by 8 day(s)•Due by June 15, 2025
- Overdue by 8 day(s)•Due by June 15, 2025
- Overdue by 1 month(s)•Due by May 15, 2025
- Overdue by 3 month(s)•Due by March 25, 2025
- Overdue by 3 month(s)•Due by March 1, 2025
- Overdue by 4 month(s)•Due by January 28, 2025•1/2 issues closed
- Overdue by 9 month(s)•Due by September 15, 2024
Implement enough to stub out `#![feature(min_specialization)]` as it is required for handling Rust's standard library
Overdue by 3 month(s)•Due by March 1, 2025•2/2 issues closed- Overdue by 3 month(s)•Due by March 1, 2025•129/129 issues closed
- Overdue by 7 month(s)•Due by November 15, 2024
Fixes for macro expansion, specifically geared towards `core` 1.49
Overdue by 3 month(s)•Due by March 1, 2025•34/37 issues closedSome of the plugins used by Linux kernel developers require certain frontend hooks to be implemented in order to work properly - we need to research what those hooks are and implement them.
No due dateContinue the work on const generics in order to support more constructs and more real life code examples
Overdue by 9 month(s)•Due by August 30, 2024•0/1 issues closedImprovements around error handling, error reporting, dealing with invalid code, rejecting invalid code better, etc. This milestone does *not* concern the handling of valid code, which is concerned by the "Name Resolution 2.0 rework" milestone, and as such, it is very low priority.
No due date•1/2 issues closedFinish the rewrite of our name resolution pass to support previously unhandled features such as glob imports and advanced shadowing.
Overdue by 2 month(s)•Due by April 1, 2025•47/73 issues closedFinish the borrow-checking work in order to support as many borrow-checking errors as possible while simultaneously restricting unfinished behavior as much as possible
Overdue by 2 month(s)•Due by April 15, 2025•1/2 issues closedThis milestone describes the functionality that a user may expect from the `core` crate. More specifically, it targets the functionality related to macros, name resolution, macro expansion, `cfg` conditional compilation... For example, having access to the `println!` or `asm!` builtin macros and for their behaviour to be correct and in-line with `rustc`.
Overdue by 2 month(s)•Due by April 15, 2025•10/48 issues closedThings like proper error codes, an adapted test runner to compare both compilers, and the necessary infrastructure to properly check for regressions and actually starting to perform meaningful runs on the rustc testsuite.
Overdue by 1 year(s)•Due by February 1, 2024•12/13 issues closedSupport all of the patterns and features used in libcore 1.49 at the HIR level: this includes, and isn't limited to, complex match patterns, inline assembly, some of the more complex type system features such as specialization, etc.
No due date•124/150 issues closedFinish up and polish the work started for [`Procedural Macros 1`](https://github.com/Rust-GCC/gccrs/milestone/16). Once this milestone is complete, `gccrs` should have a fully fledged procedural macro expansion system with support for complex derive macros and such. This milestone will be important in order to support all proc macros used and developed by the Rust part of the Linux kernel.
Overdue by 4 month(s)•Due by February 15, 2025•8/16 issues closedThis will be an ongoing task
No due date•37/47 issues closed