Skip to content

Issues: rust-lang/rust

Draft release notes for 1.88.0
#141598 opened May 26, 2025 by Mark-Simulacrum
Open 9
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
44 Open 56 Closed
44 Open 56 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

Setting constant as an invalid function pointer is undefined behavior, but required for implementing certain C APIs in rust C-discussion Category: Discussion or questions that doesn't represent real issues. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. T-opsem Relevant to the opsem team
#141660 opened May 27, 2025 by karolherbst
8
Missed optimization: multiple instances of a small struct don't reuse the stack allocation A-codegen Area: Code generation A-MIR Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html A-mir-opt Area: MIR optimizations C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#141649 opened May 27, 2025 by ohadravid
11
&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, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#141264 opened May 19, 2025 by kupiakos
1
2
Allow volatile access to non-Rust memory, including address 0 disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#141260 opened May 19, 2025 by LuigiPiucco Loading…
1
@JakobDegen
49
Some platforms cannot provide strict IEEE-754 conformant subnormals due to real-time guarantees and/or hardware limitations A-floating-point Area: Floating point numbers and arithmetic C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#139277 opened Apr 2, 2025 by DemiMarie
28
dubious &raw const|mut value compile error A-raw-pointers Area: raw pointers, MaybeUninit, NonNull C-discussion Category: Discussion or questions that doesn't represent real issues. T-opsem Relevant to the opsem team
#139156 opened Mar 30, 2025 by Paladynee
6
core::ptr::replace implementation is unsound since Rust 1.80 C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#138351 opened Mar 11, 2025 by orlp
2
Atomic*::as_ptr unnecessarily restricts operations on the pointer to atomic operations A-atomic Area: Atomics, barriers, and sync primitives A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. T-opsem Relevant to the opsem team
#138246 opened Mar 8, 2025 by briansmith
1
Decide what to do about UnsafePinned and safe Pin::as_ref C-bug Category: This is a bug. C-discussion Category: Discussion or questions that doesn't represent real issues. F-unsafe_pinned `#![feature(unsafe_pinned)]` I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#137750 opened Feb 27, 2025 by traviscross
3
LLVM nocapture attribute is used incorrectly A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#137668 opened Feb 26, 2025 by tmiasko
1
10
"accessible" terminology in with_exposed_provenance docs is misleading A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-bug Category: This is a bug. T-opsem Relevant to the opsem team
#137060 opened Feb 15, 2025 by saethlin
5
CString being noalias is a footgun A-box Area: Our favorite opsem complication A-FFI Area: Foreign function interface (FFI) C-bug Category: This is a bug. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#136770 opened Feb 9, 2025 by theemathas
9
Support calling functions with SIMD vectors that couldn't be used in the caller 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. A-SIMD Area: SIMD (Single Instruction Multiple Data) C-feature-request Category: A feature request, i.e: not implemented / a PR. T-opsem Relevant to the opsem team WG-llvm Working group: LLVM backend code generation
#132865 opened Nov 10, 2024 by RalfJung
2
Document what a "dangling pointer" is A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. E-help-wanted Call for participation: Help is requested to fix this issue. L-dangling_pointers_from_temporaries Lint: dangling_pointers_from_temporaries T-libs Relevant to the library team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#132286 opened Oct 28, 2024 by Urgau
3 tasks
15
with_exposed_provenance(0).with_addr(addr) is compiled as gep null A-strict-provenance Area: Strict provenance for raw pointers C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#131741 opened Oct 15, 2024 by saethlin
5
Compilation error when matching reference to empty enum A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-patterns Relating to patterns and pattern matching C-bug Category: This is a bug. F-exhaustive_patterns `#![feature(exhaustive_patterns)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team T-types Relevant to the types team, which will review and decide on the PR/issue.
#131452 opened Oct 9, 2024 by dhedey
@Nadrieril
26
Further restricting what coercions are allowed on places of type ! A-coercions Area: implicit and explicit `expr as Type` coercions C-discussion Category: Discussion or questions that doesn't represent real issues. F-never_type `#![feature(never_type)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#131297 opened Oct 5, 2024 by compiler-errors
6
Unexpected unsizing coercion introduced by unsafe block A-MIR Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html T-opsem Relevant to the opsem team T-types Relevant to the types team, which will review and decide on the PR/issue.
#128880 opened Aug 9, 2024 by RalfJung
3
Can CFI be made compatible with type erasure schemes? A-control-flow-integrity Area: Control Flow Integrity (CFI) security mitigation A-sanitizers Area: Sanitizers for correctness and code quality C-discussion Category: Discussion or questions that doesn't represent real issues. PG-exploit-mitigations Project group: Exploit mitigations T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#128728 opened Aug 6, 2024 by RalfJung
28
Miscompilation of a program projecting field of an extern type A-mir-opt Area: MIR optimizations C-bug Category: This is a bug. F-extern_types `#![feature(extern_types)]` I-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness 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-opsem Relevant to the opsem team
#127336 opened Jul 4, 2024 by tmiasko
What should SIMD bitmasks look like? A-SIMD Area: SIMD (Single Instruction Multiple Data) C-discussion Category: Discussion or questions that doesn't represent real issues. PG-portable-simd Project group: Portable SIMD (https://github.com/rust-lang/project-portable-simd) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#126217 opened Jun 10, 2024 by RalfJung
6
Allow moving out of &'static mut T C-discussion Category: Discussion or questions that doesn't represent real issues. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#125868 opened Jun 1, 2024 by Ddystopia
17
Tracking Issue for RFC 3467: UnsafePinned B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-unsafe_pinned `#![feature(unsafe_pinned)]` T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#125735 opened May 29, 2024 by traviscross
1 of 9 tasks
6
How should const generics with references work around pointer identity and padding? A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) F-unsized_const_params `#![feature(unsized_const_params)]` T-opsem Relevant to the opsem team
#120961 opened Feb 12, 2024 by RalfJung
1
15
What is the behavior of a place-to-value/reference conversion of a variant place? T-opsem Relevant to the opsem team
#120369 opened Jan 26, 2024 by RalfJung
3
ProTip! Mix and match filters to narrow down what you’re looking for.