Tracking Issue for derive_skip

[clubby789]

This is a tracking issue for rust-lang/libs-team#334.
The feature gate for the issue is #![feature(derive_skip)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

• Implement the APC (Implement #[skip] for builtin derives #121053)
• Adjust documentation (see instructions on rustc-dev-guide)
• Formatting for new syntax has been added to the Style Guide (nightly-style-procedure)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• How to deal with unhandled/typo arguments (e.g. #[skip(Degub)]
• Support for 3rd party derives, or just builtins
• Should #[skip = "Debug"] work?
• Handling #[skip] when not all derives support it
• Interaction with StructuralPartialEq

Implementation history

• Initial implementation (Implement #[skip] for builtin derives #121053)

[jplatte]

I wonder, if any fields are skipped in Debug, should finish_non_exhaustive be used automatically instead of plain finish?

[dead-claudia]

Related ACP: rust-lang/libs-team#334