P-E-P

Results 37 issues of P-E-P

Late name resolution was not used and did not handle globbing.

enhancement

The interface for both types is almost the same as well as the attributes. Since #2755 function body can now be optional. This means an `ExternalFunctionItem` could technically be replaced...

good-first-pr

Rust keyword should be used in a given order 1. `pub` 2. `default` 3. `const` 4. `async` 5. `unsafe` 6. `extern` Rust provides multiple messages and notes to help with...

good-first-pr
cleanup
parser

GCCRS lexer refuses literals with an unknown suffixes. I tried this code: `-frust-compile-until=ast` ```rust extern crate test_pm; use test_pm::my_macro; my_macro! { 0q 1.0q } ``` I expected to see this...

bug
good-first-pr

you can add the same check for `async` functions, even if that is about to change soon. _Originally posted by @CohenArthur in https://github.com/Rust-GCC/gccrs/pull/2753#discussion_r1411796349_ ``` error[E0706]: functions in traits cannot be...

good-first-pr

The stable crate id is required to differentiate two binaries built using different compilers. This id should be used to generate/read the proc macro entry symbol.

enhancement

Using index `0001` on an tuple should emit an error I tried this code: ```rust fn main() { (1, (2, 3)).0001.0001; } ``` I expected to see this happen: Emit...

bug

Compiler is emitting an error even if the code is disabled. I tried this code: ```rust fn main() {} #[cfg(FALSE)] trait T { default const X: u8; } ``` I...

bug
parser

Dump process shall dump all generics in order to be accurate, but an implicit `Self` generic is injected during name-resolution step. This means, the dump used for metadata export does...

bug