Proposed resolution:

This wording is relative to N4950.

[Drafting Note: There are two mutually exclusive proposed resolutions, depending on whether it is allowed to deprecate components not in [depr].

Option A:

1. Insert a paragraph at the end of [contents]:

   -?- Recommended practice: Implementations should not apply the deprecated attribute ([dcl.attr.deprecated]) to library entities that are not specified in [depr]. Implementations should apply the deprecated attribute to library entities specified in [depr] whenever possible.

Option B:

1. Insert two paragraphs at the end of [contents]:

   -?- Implementations shall not apply the deprecated attribute ([dcl.attr.deprecated]) to library entities that are not specified in [depr].

   -?- Recommended practice: Implementations should apply the deprecated attribute to library entities specified in [depr] whenever possible.

[ St. Louis 2024-06-24 Status changed: Tentatively NAD → NAD. ]

[ 2023-06-01; Reflector poll ]

Set status to Tentatively NAD after nine votes in favour during reflector poll. Let implementations decide when to apply these attributes.

[depr.general]/2 allows implementations to apply the deprecated attribute to deprecated components. However, there doesn't seem to be any wording disallowing applying the deprecated attribute to non-deprecated components.

Is it intended to allow implementations to deprecate every library component as they want? If so, should we turn the allowance into "Recommended practice" and move it to somewhere in [requirements]?

There doesn't seem to be wording which formally recommends applying deprecated attribute to deprecated components either.