g the
> >>> aliases of Align16 and Align64 from byte arrays to uint16/uint64
> >>> would fix this.
> >>>
> >>> On Wed, Jun 11, 2025, 15:47 Robert Engels >>> <mailto:ren...@ix.netcom.com>> wrote:
> >>>
> >>> I don’
current version of Go.
Timur Celik schrieb am Dienstag, 10. Juni 2025 um 17:03:31 UTC+2:
> Consider the following generic type, which ensures to be large enough by
> allocating enough padding A and the to-be-aligned type T:
>
> type Alignment interface {
> Align16 | Align64
> }
&g
Consider the following generic type, which ensures to be large enough by
allocating enough padding A and the to-be-aligned type T:
type Alignment interface {
Align16 | Align64
}
type Align16 = [16]byte
type Align64 = [64]byte
type Aligned[T any, A Alignment] struct {
pad A
val T
}
func (p *Alig
Thank you so much, this solves my issue. Really appreciate your work for
the Go project, Ian. Cheers
Ian Lance Taylor schrieb am Mi., 4. Okt. 2023, 18:05:
> On Wed, Oct 4, 2023 at 5:36 AM Timur Celik wrote:
> >
> > Why is it that changes in the runtime package's atomic.Cas
Why is it that changes in the runtime package's atomic.Cas don't land in
my build? I suspect it has something to do with inlining of the
function, but even with `-gcflags=-l` the atomic.Cas original
implementation seems to get inlined. Functions that aren't inlined,
like atomic.Or have my changes
