deprecated and deprecated_after should not be separate attributes #19138
Description
Describe the feature
These 2 attributes should be combined into a single attribute, because you should never be allowed to make something deprecated without specifying a date where it will become an error to use it. You also shouldn't be allowed to mark something deprecated with a date, but no message.
Alex agrees with the idea: https://discord.com/channels/592103645835821068/592106336838352923/1133052769280995369
Use Case
It is frustrating to see a deprecation notice without a message, or to see a message, but it never turns into an error.
Proposed Solution
Alex's suggestion is [deprecated('xxx', '2100-01-01')] - doesn't matter that much to me, as long as the 2 attributes are combined.
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
Version used
All
Environment details (OS name and version, etc.)
All