bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Rollup merge of #110859 - compiler-errors:no-negative-drop-impls, r=oli-obk

Browse source 
Explicitly reject negative and reservation drop impls

Fixes #110858

It doesn't really make sense for a type to have a `!Drop` impl. Or at least, I don't want us to implicitly assign a meaning to it by the way the compiler *currently* handles it (incompletely), and rather I would like to see a PR (or an RFC...) assign a meaning to `!Drop` if we actually wanted one for it.
This commit is contained in:
Matthias Krüger 2023-05-04 08:09:03 +02:00 • committed by GitHub
commit 6fca1a9259
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 74 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

4
compiler/rustc_hir_analysis/messages.ftl
View file

@ -280,3 +280,7 @@ hir_analysis_const_specialize = cannot specialize on const impl with non-const i
hir_analysis_static_specialize = cannot specialize on `'static` lifetime
hir_analysis_missing_tilde_const = missing `~const` qualifier for specialization
hir_analysis_drop_impl_negative = negative `Drop` impls are not supported
hir_analysis_drop_impl_reservation = reservation `Drop` impls are not supported