diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-04 08:09:03 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-04 08:09:03 +0200 |
| commit | 6fca1a925985105e4393bbca227f868ee2de5c96 (patch) | |
| tree | a17338ec1a8a911d960a26804f7bd912ca9ba378 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 129195f57c02c8a8e4cfc4b766d4ff7a3a837882 (diff) | |
| parent | bd146c72ac2faf6bbf189ad92d06e0bcd6cc92fc (diff) | |
| download | rust-6fca1a925985105e4393bbca227f868ee2de5c96.tar.gz rust-6fca1a925985105e4393bbca227f868ee2de5c96.zip | |
Rollup merge of #110859 - compiler-errors:no-negative-drop-impls, r=oli-obk
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.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions