Closed Patryk27 closed 2 years ago
Compiling this code:
#[derive(Document)] struct Foo { bar: Bar, } struct Bar;
... will throw the trait bound ... is not satisfied at Document - it'd be nice if we pointed out bar: Bar instead, as does e.g. Serde.
the trait bound ... is not satisfied
Document
bar: Bar
Closing as inactionable; Serde's example yields a pretty nice error message, because Serde generates self.bar.serialize(...) underneath, which the compiler simply pretty-prints in a nice way.
self.bar.serialize(...)
Compiling this code:
... will throw
the trait bound ... is not satisfied
atDocument
- it'd be nice if we pointed outbar: Bar
instead, as does e.g. Serde.