The rules for attributes specified in the standard are defined where they
can be applied for each attribute.
And I propose some which to use with policy code blocks but I don't have
objections to extend list.

On Fri, Nov 29, 2024 at 11:08 AM Sebastian Wittmeier via Std-Proposals <
std-proposals_at_[hidden]> wrote:

> "The following attributes/keywords are proposed as initially supported
> within policy blocks:"
>
> So it could hardcode, where to apply those.
>
>
> -----Ursprüngliche Nachricht-----
> *Von:* Artur z Redy via Std-Proposals <std-proposals_at_[hidden]>
> *Gesendet:* Fr 29.11.2024 10:40
> *Betreff:* Re: [std-proposals] Proposal for policy scopes and attribute
> aliases in C++
> *An:* std-proposals_at_[hidden];
> *CC:* Artur z Redy <arturbac.ab_at_[hidden]>;
> "Would the attributes be applied to 'everything' or only to the respective
> entity type, e.g. [[nodiscard]] to functions only."
> take a look at 3.
> "There are standard attributes and custom attributes, e.g. by
> implementations, tooling."
> take a look at 1.2
>
> On Fri, Nov 29, 2024 at 9:14 AM Sebastian Wittmeier via Std-Proposals <
> std-proposals_at_[hidden]> wrote:
>
> Would the attributes be applied to 'everything' or only to the respective
> entity type, e.g. [[nodiscard]] to functions only.
>
>
>
> In the second case, where is it defined, which attribute is for what kind
> of entity?
>
>
>
> There are standard attributes and custom attributes, e.g. by
> implementations, tooling.
>
>
>
> And by the program: With reflection the code itself can read back
> attributes.
>
>
>
> So it is observable, which entity gets the attribute.
>
>
>
>
> -----Ursprüngliche Nachricht-----
> *Von:* Artur z Redy via Std-Proposals <std-proposals_at_[hidden]>
> *Gesendet:* Fr 29.11.2024 09:00
> *Betreff:* [std-proposals] Proposal for policy scopes and attribute
> aliases in C++
> *An:* std-proposals_at_[hidden];
> *CC:* Artur z Redy <arturbac.ab_at_[hidden]>;
> I'm submitting a proposal for policy scopes and attribute aliases in C++
> that aims to simplify attribute management across large codebases,
> particularly focusing on making error handling with std::expected safer by
> default while reducing maintenance overhead - I would greatly appreciate
> the review and feedback.
>
> https://github.com/arturbac/policy_scope
>
> -- Std-Proposals mailing list Std-Proposals_at_[hidden] https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>