Expand `derive` documentation.

[ehuss]

The derive attribute documentation should probably list the built-in traits that are derivable. To my knowledge, the list is:

• Clone
• Hash
• PartialEq
• Eq
• PartialOrd
• Ord
• Debug
• Default
• Send
• Sync
• Copy

Should the documentation also specify the semantics of how the default implementations behave? It seems like important information, but I think it is mostly covered in the core/std docs. Another option is to link to https://doc.rust-lang.org/book/appendix-03-derivable-traits.html.

[Mark-Simulacrum]

Send and Sync to my knowledge can't be derived -- they're auto-implemented by the compiler where applicable and are otherwise unsafe to implement.

[ehuss]

Oops, I had just copy/pasted from the code and didn't pay attention.

[Centril]

Should the documentation also specify the semantics of how the default implementations behave? It seems like important information, but I think it is mostly covered in the core/std docs.

Yes, the reference should strive to be the source of truth to which everything links, not the other way around. (caveat for things about rustc and notes...) The info should be here.

[lcnr]

We should also document:

• the standard library derive also looks at fields and adds bounds for T::Assoc, but not <T as Trait>::Assoc buitlin-derive constrains non-qualified paths lcnr/random-rust-snippets#8
• to do this, it does not allow macro's in type position builtin-derive errors when encountering macros in type position lcnr/random-rust-snippets#9