> What is that even supposed to mean?!

It's a term used to describe a practice that shouldn't work but it does in practice because of an unanticipated obscure feature and nobody understand why.


-----Original Message-----
From: Jan Schultke <janschultke_at_[hidden]>
Sent: Thursday, September 4, 2025 08:31
To: Tiago Freire <tmiguelf_at_hotmail.com>
Cc: std-proposals_at_[hidden]
Subject: Re: [std-proposals] D3666R0 Bit-precise integers

> I do mean bytes, not bits.
> a function can return anything, what I was referencing is the fact that _BitInt(384) can not be used to access specialized registers, so a different type is required to do that.
> It can't because of 1. alignment requirements, even registers don't have alignment, the type must be swappable into memory.

Yeah, that "swapping" happens using load and store instructions that operate on such a specialized register. Nothing prevents operations on
_BitInt(384) from being compiled down to such loads and stores.

> 2. That is not defined, making voodoo programing at best.

What is that even supposed to mean?!