Skip to content

Issues: rust-lang/rust

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
73 Open 84 Closed
73 Open 84 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Assignment into Deref is allowed and creates irrelevant errors A-diagnostics Area: Messages for errors, warnings, and lints D-confusing Diagnostics: Confusing error or lint that should be reworked. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#130326 opened Sep 13, 2024 by kornelski
4
E0050 emitted unexpectedly on missing : A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The parsing of Rust source code to an AST D-confusing Diagnostics: Confusing error or lint that should be reworked. D-papercut Diagnostics: An error or lint that needs small tweaks. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#129273 opened Aug 19, 2024 by lolbinarycat
Duplicate error messages when RPIT comes from function whose generics don't satisfy bounds A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. D-confusing Diagnostics: Confusing error or lint that should be reworked. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-types Relevant to the types team, which will review and decide on the PR/issue.
#128756 opened Aug 6, 2024 by Baptistemontan
@compiler-errors
5
Unused generic types result in confusing error messages A-diagnostics Area: Messages for errors, warnings, and lints D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#128644 opened Aug 4, 2024 by lukasvrenner
Verbose, confusing error message, with a lot of extension traits in scope with the same method name A-diagnostics Area: Messages for errors, warnings, and lints A-traits Area: Trait system D-confusing Diagnostics: Confusing error or lint that should be reworked. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#128540 opened Aug 2, 2024 by Philipp-M
1
Error code E0116 causes high volume of incorrect compiler errors A-diagnostics Area: Messages for errors, warnings, and lints D-confusing Diagnostics: Confusing error or lint that should be reworked. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125814 opened May 31, 2024 by anthonydandrea
4
E0277 Emitted Twice A-diagnostics Area: Messages for errors, warnings, and lints A-traits Area: Trait system D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125685 opened May 28, 2024 by veera-sivarajan
@compiler-errors
1
When a trait is missing items, there are many follow-up errors distracting from the root cause A-diagnostics Area: Messages for errors, warnings, and lints D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125603 opened May 27, 2024 by RalfJung
1
long literal expressions should be truncated A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125581 opened May 26, 2024 by lolbinarycat
21
Associated function from super traits not accessible via sub traits A-associated-items Area: Associated items (types, constants & functions) A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name resolution A-trait-objects Area: trait objects, vtable layout C-bug Category: This is a bug. D-incorrect Diagnostics: A diagnostic that is giving misleading or incorrect information. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124438 opened Apr 27, 2024 by WaffleLapkin
3
Spurious “constant provided when a type was expected” upon syntax error in a generic parameter list A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The parsing of Rust source code to an AST D-confusing Diagnostics: Confusing error or lint that should be reworked. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124298 opened Apr 23, 2024 by kpreid
@fmease
1
Confusing error message on using step_by and take on infinite iterator A-diagnostics Area: Messages for errors, warnings, and lints A-traits Area: Trait system C-bug Category: This is a bug. D-confusing Diagnostics: Confusing error or lint that should be reworked. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#123637 opened Apr 8, 2024 by arnabanimesh
Diagnostic regression for proc-macro generated code A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example P-medium Medium priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another.
#123503 opened Apr 5, 2024 by weiznich
3
Wrong error emitted with multiple traits in return position of trait function A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#122193 opened Mar 8, 2024 by LWEdslev
1
Errors about unknown attributes when attr macro failed to resolve A-attributes Area: Attributes (`#[…]`, `#![…]`) A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name resolution D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#121555 opened Feb 24, 2024 by Noratrieb
1
An nbsp isn’t treated as whitespace but instead throws an error A-parser Area: The parsing of Rust source code to an AST D-papercut Diagnostics: An error or lint that needs small tweaks. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118874 opened Dec 12, 2023 by TheBlckbird
2
Could unused_imports be suppressed when there are name resolution failures? A-diagnostics Area: Messages for errors, warnings, and lints D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118303 opened Nov 26, 2023 by scottmcm
1
rustc should not try to analyze the crate after "multiple candidates" messages A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118130 opened Nov 21, 2023 by RalfJung
1
Error recovery after errors during macro expansion is usually futile A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#116180 opened Sep 26, 2023 by Noratrieb
@policeakshithreddy
10
multiple spurious errors when T: 'static is required in async fn A-borrow-checker Area: The borrow checker A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#115376 opened Aug 30, 2023 by aliemjay
Tweak output of E0599 to make it less verbose A-diagnostics Area: Messages for errors, warnings, and lints D-papercut Diagnostics: An error or lint that needs small tweaks. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#114430 opened Aug 3, 2023 by estebank
1
On linker errors write command to file instead of printing to disk A-diagnostics Area: Messages for errors, warnings, and lints A-linkage Area: linking into static, shared libraries and binaries D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#110763 opened Apr 24, 2023 by estebank
4
Hide .o files in linker errors by default A-diagnostics Area: Messages for errors, warnings, and lints A-linkage Area: linking into static, shared libraries and binaries D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#109979 opened Apr 5, 2023 by jyn514
1
5
warn(semicolon_in_expressions_from_macros) interacts poorly with macros invalid in expression context A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#109236 opened Mar 16, 2023 by CAD97
1
Distracting additional information when u64 is passed to the .pow() method of another u64 A-diagnostics Area: Messages for errors, warnings, and lints D-papercut Diagnostics: An error or lint that needs small tweaks. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#108844 opened Mar 7, 2023 by miikkas
ProTip! no:milestone will show everything without a milestone.