On 8/22/24 18:22, René Ferdinand Rivera Morell via Std-Proposals wrote:
> On Thu, Aug 22, 2024 at 10:00 AM Mike Reed via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
>>
>> Given that nearly every use case is to produce a unique identifier, surely the last thing you want overflow to do is silently wrap to zero. I would expect the standard to mandate that overflow forces a compile error.
>
> Given that.. It would be more useful to standardize some form of
> __UUID__ that matches the current __COUNTER__ use cases.

I think, it would make ODR issues even worse than __COUNTER__. Imagine
__UUID__ used in a header included in multiple TUs.

You could argue for some sort of hash over __FILE__ and byte offset in
the current file combined, where __FILE__ is a canonical path.