But pal its self-explanatory and the crowd can argue why and I can argue back that's how a debate circle works I thought we debate!
________________________________
From: Jens Maurer <jens.maurer_at_[hidden]>
Sent: 21 September 2026 13:20
To: std-proposals_at_[hidden] <std-proposals_at_[hidden]>
Cc: Liam Graham <liamgraham_at_[hidden]>
Subject: Re: [std-proposals] PROPOSAL: Reintroduce register — wise for developer-first decisions.


You're posting a large number of one-line thoughts to this reflector.

Please read https://isocpp.org/std/submit-a-proposal , in particular:

"Post an initial brief description of your feature on the std-proposals mailing list,
including especially the problem it solves and alternatives considered."

I find your posts seriously lacking in the "especially" parts.
For example, there are various compiler extensions to allow
allocations of local variables to particular registers; it would
be great to present them alongside rationale why this is a large
enough problem to standardize a solution for.

Jens




On 9/21/26 14:08, Liam Graham via Std-Proposals wrote:
> Treat it like a storage class, not as a compiler hint
>
> Register int X["R8"]
> Or perhaps
> Register int X[0] where [N] is the register file index. The issue is calling conventions. But allow the developer to shoot themselves in the foot if they choose.
>
> #pragma register(RAX)
> [[register:RAX]]
>
> Etc etc
>