Skip to content

Issues: rust-lang/rust

Draft release notes for 1.87
#140133 opened Apr 21, 2025 by BoxyUwU
Open 5
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
46 Open 89 Closed
46 Open 89 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

rustdoc prints the names of private consts when used as const generic parameter defaults A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-const-generics Area: const generics (parameters and arguments) A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#129035 opened Aug 13, 2024 by kpreid
"impl Copy" can bypass field privacy A-trait-system Area: Trait system A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-types Relevant to the types team, which will review and decide on the PR/issue.
#128872 opened Aug 9, 2024 by RalfJung
18
Tracking issue for future-incompatibility lint pub_use_of_private_extern_crate A-crates Area: Crates and their interactions (like crate loading) A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-resolve Area: Name/path resolution done by `rustc_resolve` specifically A-visibility Area: Visibility / privacy C-future-incompatibility Category: Future-incompatibility lints C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#127909 opened Jul 18, 2024 by RalfJung
unnameable_types should show where the type is reachable A-diagnostics Area: Messages for errors, warnings, and lints A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. L-unnameable_types Lint: unnameable_types T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#126435 opened Jun 13, 2024 by kpreid
3
Error when failing to find macro should suggest pub(crate) A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-visibility Area: Visibility / privacy D-lack-of-suggestion Diagnostics: Adding a (structured) suggestion would increase the quality of the diagnostic. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#121773 opened Feb 29, 2024 by joshtriplett
4
effective visibilities: Split reachable into "reachable through interfaces" and "reachable through bounds" A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy L-private_bounds Lint: private_bounds L-private_interfaces Lint: private_interfaces T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#120149 opened Jan 19, 2024 by petrochenkov
effective visibilities: Count types leaked through trivial type aliases as reexported A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy C-enhancement Category: An issue proposing an enhancement or a PR with one. L-unnameable_types Lint: unnameable_types T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#120146 opened Jan 19, 2024 by petrochenkov
exported_private_dependencies lint only take effect in innermost dependency A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy C-bug Category: This is a bug. F-public_private_dependencies feature: public_private_dependencies L-exported_private_dependencies Lint: exported_private_dependencies T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#119428 opened Dec 22, 2023 by linyihai
21
Suggestion: Split unreachable_pub lint into multiple lints A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy C-feature-request Category: A feature request, i.e: not implemented / a PR. L-unreachable_pub Lint: unreachable_pub T-lang Relevant to the language team, which will review and decide on the PR/issue.
#112615 opened Jun 14, 2023 by jplatte
Suggest code correction for E0446 - private type in public interface A-diagnostics Area: Messages for errors, warnings, and lints A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` A-visibility Area: Visibility / privacy T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#112284 opened Jun 4, 2023 by nyurik
2
@aryan-debug
2
Trait fn impl takes precedence over concrete type's fn impl depending on visibility A-trait-system Area: Trait system A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-types Relevant to the types team, which will review and decide on the PR/issue.
#111443 opened May 10, 2023 by rljacobson
unreachable_pub lint does not fire in the case of partial wildcard shadowing A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-resolve Area: Name/path resolution done by `rustc_resolve` specifically A-visibility Area: Visibility / privacy C-bug Category: This is a bug. L-unreachable_pub Lint: unreachable_pub T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#111360 opened May 8, 2023 by jamesmunns
3
unreachable_pub lint suggests a breaking fix for associated type on trait A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy C-bug Category: This is a bug. L-unreachable_pub Lint: unreachable_pub T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#110923 opened Apr 28, 2023 by mpalmer
Nested module privacy hole doesn't trigger lints A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#109709 opened Mar 28, 2023 by workingjubilee
2
Alleged type visibility leakage A-visibility Area: Visibility / privacy C-bug Category: This is a bug.
#108457 opened Feb 25, 2023 by fengalin
1
@GuillaumeGomez
5
"bad" error message for inferred trait type arguments. A-diagnostics Area: Messages for errors, warnings, and lints A-visibility Area: Visibility / privacy T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#104784 opened Nov 23, 2022 by downloadpizza
@mox692
2
weird "private trait" errors around ptr::metadata for public struct wrapping private trait object A-diagnostics Area: Messages for errors, warnings, and lints A-trait-system Area: Trait system A-visibility Area: Visibility / privacy C-bug Category: This is a bug. D-confusing Diagnostics: Confusing error or lint that should be reworked. D-imprecise-spans Diagnostics: spans don't point to exactly the erroneous code D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#97984 opened Jun 11, 2022 by ben0x539
Coherence issue when using crate-local traits with type parameters A-coherence Area: Coherence A-trait-system Area: Trait system A-visibility Area: Visibility / privacy C-enhancement Category: An issue proposing an enhancement or a PR with one. T-types Relevant to the types team, which will review and decide on the PR/issue.
#97811 opened Jun 6, 2022 by ghananigans
1
Watch out for modules privacy when proposing traits to associate with an item A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` A-visibility Area: Visibility / privacy D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#95080 opened Mar 18, 2022 by catenacyber
1
rustdoc: Inlining a foreign public struct with private fields shows the fields as private in the current crate A-cross-crate-reexports Area: Documentation that has been re-exported from a different crate A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#91440 opened Dec 1, 2021 by jyn514
4
Leaking private structs in public functions A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#85883 opened Jun 1, 2021 by conradludgate
13
Private supertraits are not callable on concrete types A-trait-system Area: Trait system A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#83882 opened Apr 5, 2021 by MaikKlein
4
Imprecise visibility error message A-diagnostics Area: Messages for errors, warnings, and lints A-visibility Area: Visibility / privacy D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#82872 opened Mar 7, 2021 by vchekan
"Consider importing one of these" diagnostic should perhaps not suggest use statements from the parent module A-diagnostics Area: Messages for errors, warnings, and lints A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` A-visibility Area: Visibility / privacy C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#82358 opened Feb 21, 2021 by Manishearth
1
Nonlinearity in check_mod_privacy pass for a large number of impls A-visibility Area: Visibility / privacy C-bug Category: This is a bug. I-slow Issue: Problems and improvements with respect to performance of generated code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#81263 opened Jan 22, 2021 by weiznich
ProTip! Updated in the last three days: updated:>2025-04-26.