Tracking Issue for remove-implicit-feature RFC 3491

[ehuss]

Summary

RFC: #3491

Implementation:

• feat: Add a basic linting system #13621
• Unused dependencies cleanup #13778
• fix(fix): Address problems with implicit -> explicit feature migration #14018
• fix: Ensure dep/feature activates the dependency on 2024  #14221
  • Revert "fix: Ensure dep/feature activates the dependency on 2024" #14295
• fix: Remove implicit feature removal #14630

Documentation: TODO
Closes: #9088, #10125

Removes the implicit feature created for optional dependencies, requiring them to be explicitly stated in the [features] table with dep:foo syntax.

Note

This has been deferred out of the 2024 edition. More updates will come in the future.

Issues

• Bad error message when a strong dep features's depedency is an unused optional dependency #14016
• Have cargo add --optional <dep> create a <dep> = "dep:<dep> feature #11010
• Activation of features of non-optional dependencies breaks manifest for 2024 edition #14283

Unresolved

• Suggested adding dep:foo to the foo feature if it exists for unused optional dependencies #14017

Future Extensions

No response

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.

[ehuss]

@epage Do you want to take on implementation of this, or know someone who will? Or, if not, do you want to write mentoring instructions? I can probably do that if you don't.

[epage]

@Muscraft is taking this on atm as his test case for #12235. We should pick a time to re-evaluate and, if that isn't ready in time, we pivot and hard code all of this where it is needed.