3 ms·

Someone on the issue they made explained why Clone is "broken": https://github.com/JelteF/derive_more/issues/490#issuecomment-3037408110 https://github.com/Jelt

• deleted 1y ago
  [deleted]
• sbt567 1y ago
  from Niko's post: > In the past, we were blocked for technical reasons from expanding implied bounds and supporting perfect derive, but I believe we have resolved those issues. So now we have to think a bit about semver and decide how much explicit we want to be.
• samsartor 1y ago
  I have a crate with a "perfect" derive macro that generates where clauses from the fields instead of putting them on the generic parameters. It is nice when it works, but yah cyclical trait matching is still a real problem. I wound up needing an attribute to manually override the bounds whenever they blow up: https://docs.rs/inpt/latest/inpt/#bounds https://docs.rs/inpt/latest/inpt/#bounds
  • mmastrac 1y ago
    I did a similar thing for derive-io. It greatly improved the ergonomics of the macro. https://docs.rs/derive-io/latest/derive_io/ https://docs.rs/derive-io/latest/derive_io/ Being able to handle directly recursive type bounds would be an awesome improvement to the compiler, IMO.