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
13 Open 56 Closed
13 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
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

parallel rustc: async closures not reproducible A-async-closures `async || {}` A-parallel-compiler Area: parallel compiler A-reproducibility Area: Reproducible / deterministic builds C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140425 opened Apr 29, 2025 by matthiaskrgr
async closure does not implement FnMut because it captures state from its environment for async move closures capturing copyable values, while closures returning async move blocks work fine A-async-closures `async || {}` C-bug Category: This is a bug. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140403 opened Apr 28, 2025 by ProbstDJakob
[async closure] implementation of Send is not general enough using tokio channel A-async-closures `async || {}` A-auto-traits Area: auto traits (e.g., `auto trait Send {}`) A-concurrency Area: Concurrency C-bug Category: This is a bug. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged.
#139475 opened Apr 7, 2025 by Banyc
1
AsyncFnOnce(…) and FnOnce<(…), Output : Future> are not equivalent A-async-closures `async || {}` 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-types Relevant to the types team, which will review and decide on the PR/issue.
#139173 opened Mar 31, 2025 by danielhenrymantilla
@compiler-errors
4
async closure argument type inference error has wrong span A-async-closures `async || {}` A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139150 opened Mar 30, 2025 by cyrgani
Compiler error "implementation of Send is not general enough" when using static lifetime reference with async closure A-async-closures `async || {}` A-lifetimes Area: Lifetimes / regions A-trait-system Area: Trait system C-bug Category: This is a bug. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#138494 opened Mar 14, 2025 by zhuerzhuer
Can't compile the use of impl AsyncFn within a spawned thread A-async-closures `async || {}` A-diagnostics Area: Messages for errors, warnings, and lints 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.
#138207 opened Mar 8, 2025 by jephthia
1
Type inference issue with || async {} closure in AsyncFn A-async-closures `async || {}` C-bug Category: This is a bug. 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.
#136696 opened Feb 7, 2025 by ThriceCola
2
Higher ranked lifetime error when checking auto traits of async functions containing calls to async closures which capture a local A-async-closures `async || {}` A-auto-traits Area: auto traits (e.g., `auto trait Send {}`) C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134997 opened Jan 1, 2025 by jdonszelmann
8
Invalid suggestion for AsyncFnOnce trait object A-async-closures `async || {}` A-diagnostics Area: Messages for errors, warnings, and lints A-dyn-trait Area: trait objects, vtable layout T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134182 opened Dec 11, 2024 by ehuss
@compiler-errors
2
dyn AsyncFn generates many independent errors A-async-closures `async || {}` A-diagnostics Area: Messages for errors, warnings, and lints A-dyn-trait Area: trait objects, vtable layout 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.
#132713 opened Nov 6, 2024 by cramertj
1
@cramertj
1
rustdoc: support for async Fn* trait bounds A-async-closures `async || {}` C-bug Category: This is a bug. S-blocked Status: Blocked on something else such as an RFC or other implementation work. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#127227 opened Jul 1, 2024 by fmease
3
Investigate getting rid of the AsyncFn* family of traits in favor of LendingFn* A-async-closures `async || {}` C-cleanup Category: PRs that clean code up or issues documenting cleanup. 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.
#120694 opened Feb 6, 2024 by compiler-errors
@compiler-errors
ProTip! Mix and match filters to narrow down what you’re looking for.