Skip to content

Destructors cause warnings about explicit modes #3596

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

Jump to bottom
Closed
catamorphism opened this issue Sep 26, 2012 · 1 comment
Closed

Destructors cause warnings about explicit modes #3596

catamorphism opened this issue Sep 26, 2012 · 1 comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR)
Milestone
0.4

Comments

@catamorphism
Copy link
Contributor

With deprecated_modes set to warn or forbid, the compiler complains about argument 1 of drop for anything that has a destructor. This is confusing to the user, but happens because dtors implicitly have an argument (whose mode is always by_ref). I'm on it.
@ghost ghost assigned catamorphism Sep 26, 2012
@catamorphism
Copy link
Contributor Author

Fixed -- I forgot to close this.

@catamorphism catamorphism removed their assignment Jun 16, 2014
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@topecongiro
Merge pull request rust-lang#3596 from rchaser53/issue-3595
1922094 
add tests for issue-3595
RalfJung pushed a commit to RalfJung/rust that referenced this issue May 19, 2024
@bors
Auto merge of rust-lang#3596 - bend-n:support_fstar_algebraic, r=Ralf…
32b2238 
…Jung

support `f*_algebraic`

supports the [`f*_algebraic`](https://doc.rust-lang.org/std/intrinsics/fn.fadd_algebraic.html) intrinsics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR)
Projects
None yet
Milestone
0.4
Development

No branches or pull requests
1 participant
@catamorphism