On Tue, Mar 12, 2024 at 9:53 AM Andrei Grosu via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> If a malicious actor got inside my company and can freely access ‘ide’s and my build system, any hypotetical security considerations are moot.
>
> Code can be validated cryptographically, along with the entire build system. Security-aware people have been coming up with design patterns and tools for this.
>
> If this is a security risk, which it is, I’m not denying , then maybe the ISO board should wake up and realize it’s 2024 and some security considerations for the language are long overdue. I mean Java baked this into the language a gazillion years ago.
>
> Just saying that it’s bad and it should not be used is not very useful.

Here's the thing though. You're the one proposing the feature. You are
therefore the one who has to justify it. You have to provide reasoning
as to why it's important for C++ to have this feature.

You started with the use case of a build system, but then you
backtracked and don't want to talk about that anymore. OK, but now
your proposal has no motivation. And therefore, it's bad by default.