Public
- Public
- Network
- Groups
- Popular
- People

Conversation

Notices

Masaki Hara (qnighy@qnmd.info)'s status on Saturday, 19-Jan-2019 16:39:17 JST Masaki Hara

https://internals.rust-lang.org/t/can-we-deprecate-t-drop-trait-bounds/9238
T: Drop, dyn Drop, impl DropなどDropを含むトレイト制約を禁止してはという提案。ぼくも同じことを考えてた。ただ間違えてDropを使っているケースはあるので禁止は難しいと思う。
In conversation Saturday, 19-Jan-2019 16:39:17 JST from qnmd.info permalink
Attachments
1. Domain not in remote thumbnail source whitelist: discourse-cdn-sjc1.com
  
  Can we deprecate 'T: Drop' trait bounds?
  
  from Rust Internals
  
  Is there any legitimate use for a T: Drop trait bound? As far as I can tell: There are no methods you can call on a T: Drop. AFAICT the only thing that such a bound enables you do is to unsize a value to dyn Drop. (but what good is dyn Drop for?) Usage of T: Drop for specialization is dangerous and wrong. The type (Vec, Vec) does not impl Drop. You should specialize on Copy instead.

Feeds