-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Issues: rust-lang/rust
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[E0521] coroutine should own upvars and assigning internal references to moved captures does not leak the references
A-coroutines
Area: Coroutines
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
F-coroutines
`#![feature(coroutines)]`
#140132
opened Apr 21, 2025 by
dingxiangfei2009
Initial Area: Coroutines
F-coroutines
`#![feature(coroutines)]`
F-unsafe_pinned
`#![feature(unsafe_pinned)]`
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
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)
UnsafePinned
implementation [Part 2: Lowering]
A-coroutines
Coroutine/Future Area: Coroutines
C-bug
Category: This is a bug.
E-needs-investigation
Call for partcipation: This issues needs some investigation to determine current status
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.
WG-async
Working group: Async & await
Send
bounds are too restrictive when taking references to !Sync
values
A-coroutines
#132382
opened Oct 31, 2024 by
ds84182
ICE: Unstable option: MIR validation
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
A-destructors
Area: Destructors (`Drop`, …)
C-bug
Category: This is a bug.
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.
Building async destructor constructor shim is not yet implemented for type: Coroutine
-Zvalidate-mir
#132103
opened Oct 24, 2024 by
matthiaskrgr
regression on nightly-2024-03-16
A-coroutines
Area: Coroutines
C-bug
Category: This is a bug.
F-coroutines
`#![feature(coroutines)]`
F-impl_trait_in_assoc_type
`#![feature(impl_trait_in_assoc_type)]`
P-medium
Medium priority
regression-untriaged
Untriaged performance or correctness regression.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#122618
opened Mar 17, 2024 by
xxchan
E0308 for coroutines kinda cryptic
A-coroutines
Area: Coroutines
A-diagnostics
Area: Messages for errors, warnings, and lints
F-coroutines
`#![feature(coroutines)]`
S-waiting-on-author
Status: This is awaiting some action (such as code changes or more information) from the author.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#118954
opened Dec 14, 2023 by
matthiaskrgr
"Implementation not general enough" with async and projection, fixed by wrapping with Area: Async & Await
A-coroutines
Area: Coroutines
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
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.
async move
A-async-await
#110339
opened Apr 14, 2023 by
tmandry
Tracking issue for incorrect lifetime bound errors in async
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
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.
WG-async
Working group: Async & await
#110338
opened Apr 14, 2023 by
tmandry
1 of 25 tasks
Unexpected higher-ranked lifetime error in GAT usage
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
A-GATs
Area: Generic associated types (GATs)
A-higher-ranked
Area: Higher-ranked things (e.g., lifetimes, types, trait bounds aka HRTBs)
A-lifetimes
Area: Lifetimes / regions
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-bug
Category: This is a bug.
S-bug-has-test
Status: This bug is tracked inside the repo by a `known-bug` test.
T-types
Relevant to the types team, which will review and decide on the PR/issue.
#100013
opened Aug 1, 2022 by
ethe
Generators should be able to yield references to local variables
A-coroutines
Area: Coroutines
#98740
opened Jun 30, 2022 by
M1cha
Incorrect "implementation of Area: Async & Await
A-coroutines
Area: Coroutines
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Send
is not general enough" error with lifetimed Send
impl used in async fn
A-async-await
#96865
opened May 9, 2022 by
SabrinaJewson
MIR generation for generators considers any borrowed or assigned value as live across yield points
A-borrow-checker
Area: The borrow checker
A-coroutines
Area: Coroutines
A-MIR
Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
#94067
opened Feb 16, 2022 by
eholk
Which MIR passes should run on generator drop shims?
A-coroutines
Area: Coroutines
A-MIR
Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#91576
opened Dec 6, 2021 by
ecstatic-morse
Inline generators before state machine conversion in order to reduce branching
A-coroutines
Area: Coroutines
A-mir-opt
Area: MIR optimizations
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
C-optimization
Category: An issue highlighting optimization opportunities or PRs implementing such
I-slow
Issue: Problems and improvements with respect to performance of generated code.
#83101
opened Mar 14, 2021 by
pcwalton
Tracking issue for generator code quality
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-optimization
Category: An issue highlighting optimization opportunities or PRs implementing such
I-heavy
Issue: Problems and improvements with respect to binary size of generated code.
I-slow
Issue: Problems and improvements with respect to performance of generated code.
metabug
Issues about issues themselves ("bugs about bugs")
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#71407
opened Apr 21, 2020 by
tmandry
1 task
[codegen] unnecessary panicking branch in Area: Async & Await
A-codegen
Area: Code generation
A-coroutines
Area: Coroutines
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
C-optimization
Category: An issue highlighting optimization opportunities or PRs implementing such
I-heavy
Issue: Problems and improvements with respect to binary size of generated code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
foo().await
(vs equivalent FutureImpl.await
)
A-async-await
#71093
opened Apr 13, 2020 by
japaric
Tracking Issue for Coroutine Memory Usage
A-async-await
Area: Async & Await
A-codegen
Area: Code generation
A-coroutines
Area: Coroutines
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-optimization
Category: An issue highlighting optimization opportunities or PRs implementing such
F-coroutines
`#![feature(coroutines)]`
I-heavy
Issue: Problems and improvements with respect to binary size of generated code.
metabug
Issues about issues themselves ("bugs about bugs")
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#69826
opened Mar 8, 2020 by
jonas-schievink
2 of 7 tasks
Tracking issue for more precise coroutine captures
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
A-type-system
Area: Type system
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
E-hard
Call for participation: Hard difficulty. Experience needed to fix: A lot.
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.
#69663
opened Mar 3, 2020 by
tmandry
6 of 7 tasks
Yield reference in coroutine with GAT
A-associated-items
Area: Associated items (types, constants & functions)
A-coroutines
Area: Coroutines
A-GATs
Area: Generic associated types (GATs)
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
F-coroutines
`#![feature(coroutines)]`
GATs-triaged
Issues using the `generic_associated_types` feature that have been triaged
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
#69268
opened Feb 18, 2020 by
cynecx
Coroutines should be able to implement Area: Coroutines
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
F-coroutines
`#![feature(coroutines)]`
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
for<'a> Coroutine<&'a mut T>
A-coroutines
#68923
opened Feb 7, 2020 by
jonas-schievink
Strange cycles perfomance with generators and very slow Area: Coroutines
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
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.
for
in debug
build [on nightly]
A-coroutines
#67175
opened Dec 9, 2019 by
olegnn
Lifetime bounds in auto trait impls prevent trait from being implemented on generators
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
A-trait-system
Area: Trait system
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-bug
Category: This is a bug.
P-medium
Medium priority
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.
#64552
opened Sep 17, 2019 by
leo60228
Resolve unsound interaction between noalias and self-referential data (incl. generators, async fn)
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
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.
#63818
opened Aug 22, 2019 by
Mark-Simulacrum
Async fn doubles argument size
A-async-await
Area: Async & Await
A-coroutines
Area: Coroutines
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
C-optimization
Category: An issue highlighting optimization opportunities or PRs implementing such
I-heavy
Issue: Problems and improvements with respect to binary size of generated code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#62958
opened Jul 24, 2019 by
4teap
Copy trait defeats generator optimization
A-coroutines
Area: Coroutines
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
C-optimization
Category: An issue highlighting optimization opportunities or PRs implementing such
I-heavy
Issue: Problems and improvements with respect to binary size of generated code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#62952
opened Jul 24, 2019 by
tmandry
Previous Next
ProTip!
no:milestone will show everything without a milestone.