> All those poor developers need to do is use include guards. That's
> demonstrably not an unreasonable burden.

> It's high time this proposal is nuked, yet again. I'll happily do that
> in the committee if need be, but I'd prefer not wasting time on it
> there.

People are using #pragma once, standard or not. Standardizing it would
give people clearer expectations about when it is and is not ok to
use.

Jeremy

On Thu, Aug 29, 2024 at 5:57 PM Ville Voutilainen via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> On Fri, 30 Aug 2024 at 00:59, Tiago Freire via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
> > I'm unconvinced that the "bad cases" are not just a product of bad build architecture, if done properly a compiler should never be presented with multiple alternatives of the same file. And putting such requirements on compilers puts an unnecessary burden on developers to support a scenario that it is that is arguably bad practice.
>
> All those poor developers need to do is use include guards. That's
> demonstrably not an unreasonable burden.
>
> It's high time this proposal is nuked, yet again. I'll happily do that
> in the committee if need be, but I'd prefer not wasting time on it
> there.
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals