Skip to content

Issues: rust-lang/rust

Draft release notes for 1.88.0
#141598 opened May 26, 2025 by Mark-Simulacrum
Open 10
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
294 Open 449 Closed
294 Open 449 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Rustdoc reports broken-intra-doc-links for Github markdown [!IMPORTANT]-type blockquotes A-intra-doc-links Area: Intra-doc links, the ability to link to items in docs by name A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-discussion Category: Discussion or questions that doesn't represent real issues. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#141866 opened Jun 1, 2025 by Qix-
3
libtest filters should include the test crate's name in the string matched against the filter A-libtest Area: `#[test]` / the `test` library C-discussion Category: Discussion or questions that doesn't represent real issues. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. T-testing-devex Relevant to the testing devex team (testing DX), which will review and decide on the PR/issue.
#141862 opened Jun 1, 2025 by RalfJung
1
new warnings about #[inline(always)] functions missing #[target_feature(enable="sse")] A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141848 opened Jun 1, 2025 by oconnor663
1
7
Should a [..] slice pattern constitute a discriminant read A-patterns Relating to patterns and pattern matching A-slice-patterns Area: Slice patterns, https://github.com/rust-lang/rust/issues/23121 C-discussion Category: Discussion or questions that doesn't represent real issues. I-lang-nominated Nominated for discussion during a lang team meeting. P-lang-drag-2 Lang team prioritization drag level 2.https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang. T-lang Relevant to the language team
#141825 opened May 31, 2025 by meithecatte
1
Please stop using GITHUB_ACTION to change the behaviour of the build system C-discussion Category: Discussion or questions that doesn't represent real issues. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
#141813 opened May 31, 2025 by lu-zero
7
Ideas for improving mismatched_lifetime_syntaxes wording? A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-discussion Category: Discussion or questions that doesn't represent real issues. L-mismatched_lifetime_syntaxes Lint: mismatched_lifetime_syntaxes T-lang Relevant to the language team
#141752 opened May 30, 2025 by jieyouxu
We don't imply outlives-bounds from the own explicit bounds of a GAT projection A-associated-items Area: Associated items (types, constants & functions) A-GATs Area: Generic associated types (GATs) A-implied-bounds Area: Implied bounds / inferred outlives-bounds A-lifetimes Area: Lifetimes / regions C-discussion Category: Discussion or questions that doesn't represent real issues. P-low Low priority T-types Relevant to the types team, which will review and decide on the PR/issue.
#141692 opened May 28, 2025 by fmease
1
Adding use std::error::Error unexpectedly breaks lifetime inference A-lifetimes Area: Lifetimes / regions A-type-system Area: Type system C-discussion Category: Discussion or questions that doesn't represent real issues. 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.
#141673 opened May 28, 2025 by phip1611
4
Can't use fn() for C binding if C uses sentinel value A-FFI Area: Foreign function interface (FFI) C-discussion Category: Discussion or questions that doesn't represent real issues. T-opsem Relevant to the opsem team
#141660 opened May 27, 2025 by karolherbst
9
Consider folkertdev's c_variadic proposal C-discussion Category: Discussion or questions that doesn't represent real issues. F-c_variadic `#![feature(c_variadic)]` I-lang-radar Items that are on lang's radar and will need eventual work or consideration. T-lang Relevant to the language team
#141524 opened May 24, 2025 by traviscross
8
Unexpected type inference failure when comparing Vec::<T>::new() to an empty array [] A-inference Area: Type inference C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141329 opened May 21, 2025 by 623637646
1
&raw const some_union.field erroneously requires unsafe C-discussion Category: Discussion or questions that doesn't represent real issues. T-lang Relevant to the language team T-opsem Relevant to the opsem team
#141264 opened May 19, 2025 by kupiakos
1
2
some macros have scrambled "Since" versions A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-stability Area: `#[stable]`, `#[unstable]` etc. C-discussion Category: Discussion or questions that doesn't represent real issues. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#140998 opened May 14, 2025 by lolbinarycat
3
Failed to compile code targetting wasm32-wasip2 with +atomics,+bulk-memory,+mutable-globals enabled C-discussion Category: Discussion or questions that doesn't represent real issues. O-wasm32-wasip2 Target: wasm32-wasip2
#140971 opened May 13, 2025 by aryan9600
6
Possible regression with rust_panic being mangled C-discussion Category: Discussion or questions that doesn't represent real issues. 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.
#140821 opened May 8, 2025 by Qwinci
9
fn_cast! macro A-control-flow-integrity Area: Control Flow Integrity (CFI) security mitigation A-rust-for-linux Relevant for the Rust-for-Linux project A-sanitizers Area: Sanitizers for correctness and code quality C-discussion Category: Discussion or questions that doesn't represent real issues. I-lang-nominated Nominated for discussion during a lang team meeting. P-lang-drag-2 Lang team prioritization drag level 2.https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang. PG-exploit-mitigations Project group: Exploit mitigations T-lang Relevant to the language team
#140803 opened May 8, 2025 by Darksonn
30
pub use with glob import behaves differently when re-exported vs directly used A-resolve Area: Name/path resolution done by `rustc_resolve` specifically C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140694 opened May 6, 2025 by lalala-233
2
Can Redox OS implement a TOCTOU-free fs::remove_dir_all yet? A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-discussion Category: Discussion or questions that doesn't represent real issues. O-redox Operating system: Redox, https://www.redox-os.org/ T-libs Relevant to the library team, which will review and decide on the PR/issue.
#140533 opened Apr 30, 2025 by workingjubilee
@jackpot51
7
Adding wasm32-unknown-unknown to a Rust toolchain compiled against a specific LLVM revision A-linkers Area: linkers... you gotta love linkers C-discussion Category: Discussion or questions that doesn't represent real issues. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#140473 opened Apr 29, 2025 by szilardszaloki
9
Should Vec::as_ptr()/Vec::as_mut_ptr() return nullptr instead of the dangling value? C-discussion Category: Discussion or questions that doesn't represent real issues. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#140410 opened Apr 28, 2025 by cmazakas
4
Compiler crash on cross-compile: cargo build --target x86_64-pc-windows-gnu of crate egui A-linkers Area: linkers... you gotta love linkers C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140237 opened Apr 24, 2025 by John-Nagle
10
global_asm! issues LLVM error "undefined temporary symbol" for non-existent numerical labels A-global-asm Area: `global_asm!` C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140179 opened Apr 23, 2025 by pqcfox
1
Struct containing only associated type of generic may be too constraining variance wise A-variance Area: Variance (https://doc.rust-lang.org/nomicon/subtyping.html) C-discussion Category: Discussion or questions that doesn't represent real issues. T-types Relevant to the types team, which will review and decide on the PR/issue.
#140109 opened Apr 21, 2025 by krtab
rustc bad cli arg error messages doesn't respect --error-format=json A-CLI Area: Command-line interface (CLI) to the compiler A-compiletest Area: The compiletest test runner A-diagnostics Area: Messages for errors, warnings, and lints C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140101 opened Apr 21, 2025 by jieyouxu
1
inconsistent stringify! A-pretty Area: Pretty printing (including `-Z unpretty`) C-discussion Category: Discussion or questions that doesn't represent real issues.
#140060 opened Apr 20, 2025 by loynoir
2
ProTip! Find all open issues with in progress development work with linked:pr.