Mismatch between sync and async drop gen?
Open
Nobody has claimed this yet.
A-const-eval
A-monomorphization
C-bug
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I expect that the async version would panic at compile time the same way sync version does
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mismatch with the Rust Playground example linked in the issue, comparing the synchronous and asynchronous drop-generation cases. Trace the compiler behavior for both forms and determine the expected compile-time result; done means the async case consistently matches the intended synchronous behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100