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
145 Open 278 Closed
145 Open 278 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

Incoherent (?) Lifetime HRTB on associated type results in unsoundness in stable, safe code A-associated-items Area: Associated items (types, constants & functions) A-closures Area: Closures (`|…| { … }`) A-type-system Area: Type system C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-types Relevant to the types team, which will review and decide on the PR/issue.
#141713 opened May 29, 2025 by maxdexh
11
unused_assignment triggered by closure even though value is used A-closures Area: Closures (`|…| { … }`) A-diagnostics Area: Messages for errors, warnings, and lints A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. D-imprecise-spans Diagnostics: spans don't point to exactly the erroneous code L-unused_assignments Lint: unused_assignments T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141615 opened May 26, 2025 by y86-dev
4
Type annotations needed for closure with associated type A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference 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.
#140603 opened May 3, 2025 by camsteffen
1
Closure captures are inconsistent between x and x @ _ irrefutable patterns A-closures Area: Closures (`|…| { … }`) 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.
#137553 opened Feb 24, 2025 by meithecatte
1
@meithecatte
2
LUB coercions works for a function but fails for a closure A-closures Area: Closures (`|…| { … }`) A-coercions Area: implicit and explicit `expr as Type` coercions 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. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132643 opened Nov 5, 2024 by pazmank
1
ICE: encountered type variable A-closures Area: Closures (`|…| { … }`) C-bug Category: This is a bug. F-unboxed_closures `#![feature(unboxed_closures)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#131758 opened Oct 15, 2024 by matthiaskrgr
1
Closure breaks function with higher-ranked trait bound A-closures Area: Closures (`|…| { … }`) A-higher-ranked Area: Higher-ranked things (e.g., lifetimes, types, trait bounds aka HRTBs) 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.
#131677 opened Oct 14, 2024 by drewtato
1
Closure Fn* trait coercion removes other implementable Fn* traits A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference C-bug Category: This is a bug. T-types Relevant to the types team, which will review and decide on the PR/issue.
#129381 opened Aug 21, 2024 by konnorandrews
3
Mismatched types for a conditional containing closures inside method call A-closures Area: Closures (`|…| { … }`) C-bug Category: This is a bug. T-types Relevant to the types team, which will review and decide on the PR/issue.
#127525 opened Jul 9, 2024 by marmac02
@compiler-errors
ICE: error performing ParamEnvAnd { ... } possibly related to (lack of) HRTBs in closures A-closures Area: Closures (`|…| { … }`) A-higher-ranked Area: Higher-ranked things (e.g., lifetimes, types, trait bounds aka HRTBs) A-trait-system Area: Trait system C-bug Category: This is a bug. fixed-by-next-solver Fixed by the next-generation trait solver, `-Znext-solver`. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124440 opened Apr 27, 2024 by Carnagion
2
obligations_for_self_ty leaks placeholders A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference P-low Low priority T-types Relevant to the types team, which will review and decide on the PR/issue.
#124385 opened Apr 25, 2024 by lcnr
1
Strange error message when trying to call a function that takes a closure that returns a future A-async-await Area: Async & Await A-closures Area: Closures (`|…| { … }`) A-diagnostics Area: Messages for errors, warnings, and lints AsyncAwait-Triaged Async-await issues that have been triaged during a working group meeting. fixed-by-async-closures Fixed by `#![feature(async_closure)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-async Working group: Async & await
#123717 opened Apr 10, 2024 by tljubej-tbtl
4
closure rvalue not checked for WF allowing it to assume more implied bounds A-borrow-checker Area: The borrow checker A-closures Area: Closures (`|…| { … }`) A-NLL Area: Non-lexical lifetimes (NLL) C-bug Category: This is a bug. NLL-sound Working towards the "invalid code does not compile" goal T-types Relevant to the types team, which will review and decide on the PR/issue.
#123312 opened Apr 1, 2024 by aliemjay
1
-Znext-solver: ICE with closure capturing iterated variable in 2021 edition A-closures Area: Closures (`|…| { … }`) C-bug Category: This is a bug. E-needs-test Call for participation: An issue has been fixed and does not reproduce, but no test has been added. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)
#120328 opened Jan 25, 2024 by madsmtm
4
Closures needlessly capture all generic parameters from parent item in TAIT A-closures Area: Closures (`|…| { … }`) A-impl-trait Area: `impl Trait`. Universally / existentially quantified anonymous types with static dispatch. 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.
#118116 opened Nov 21, 2023 by jwong101
2
Spurious cycle when passing an existential type referencing EnumMap to closure A-closures Area: Closures (`|…| { … }`) C-bug Category: This is a bug. F-type_alias_impl_trait `#[feature(type_alias_impl_trait)]` I-cycle Issue: A query cycle occurred while none was expected T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#116380 opened Oct 3, 2023 by amatveiakin
Type inference doesn't properly handle closures that don't return A-closures Area: Closures (`|…| { … }`) A-diagnostics Area: Messages for errors, warnings, and lints A-inference Area: Type inference C-bug Category: This is a bug. D-confusing Diagnostics: Confusing error or lint that should be reworked. 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.
#111539 opened May 13, 2023 by zackw
7
Moving structs with Copy fields into closures causes surprising behavior A-closures Area: Closures (`|…| { … }`) A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#111376 opened May 9, 2023 by alexblanck
5
Closure lifetime inference influenced by non-conflicting trait impl A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference A-lifetimes Area: Lifetimes / regions A-trait-system Area: Trait system
#108441 opened Feb 25, 2023 by ds84182
Closure parameter lifetime inference erases hrtb A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference A-lifetimes Area: Lifetimes / regions C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#107589 opened Feb 2, 2023 by pigeonhands
1
cannot infer type when expression is logically negated in closure A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#106138 opened Dec 25, 2022 by Isopod
1
4
Closure Does/Doesn't compile depending purely on usage of a {} body with --edition=2021 A-borrow-checker Area: The borrow checker A-closures Area: Closures (`|…| { … }`) A-coercions Area: implicit and explicit `expr as Type` coercions 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.
#105699 opened Dec 14, 2022 by Olipro
3
Return impl for<'a> Fn(&'a) incorrectly rejected for closures A-closures Area: Closures (`|…| { … }`) A-coercions Area: implicit and explicit `expr as Type` coercions C-bug Category: This is a bug. T-types Relevant to the types team, which will review and decide on the PR/issue.
#105528 opened Dec 10, 2022 by verglasz
Rust attemts to implement FnMut for a closure consuming a 'static mut reference? A-closures Area: Closures (`|…| { … }`) A-inference Area: Type inference
#104837 opened Nov 24, 2022 by rMazeiks
Symbol-mangling (v0) should show difference between async / closure / generator A-closures Area: Closures (`|…| { … }`) A-linkage Area: linking into static, shared libraries and binaries T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#104830 opened Nov 24, 2022 by Swatinem
1
ProTip! no:milestone will show everything without a milestone.