My immediate need/use case is Clone on CertificateSigningRequest. After skimming the codebase, however, I'm getting the impression that there are many more opportunities to implement the common traits outlined in the API guidelines. @est31 also echoed this over at #17 (comment).

Prior related work:

• Add Debug to rcgen::Certificate #315 / derive Debug for non-sensitive struct types #316
• Make Certificate cloneable (derive Clone) #319
• and more, probably...

If you're amenable to eagerly implementing these traits, I think it'd be easiest (from a review standpoint) to create a pull request per trait and dedicate each PR to sweeping the codebase and nitpicking the details—similar to #316. I'm open to other approaches too.

• Copy, Clone
  • Eagerly derive Clone, Copy, where possible #341
• Debug
  • derive Debug for non-sensitive struct types #316
  • Eagerly implemented Debug trait #343
• Display
  • (Deemed not necessary for now)
• PartialEq, Eq
  • Eagerly implemented PartialEq and Eq traits #344
• PartialOrd, Ord
  • (Closed) Eagerly implemented PartialOrd and Ord traits #346
• Hash
  • (Closed) Eagerly implemented Hash trait #345
• Default
  • (Deemed not necessary for now)