There was no announcement or any documentation on this change. The change was to add a 32 byte buffer on the stack that can be used in these situations where the actual allocation determined at runtime is 32 bytes or less.
Yes, this took me by surprise. Hahahaha > On Jan 6, 2026, at 08:50, Alexander Shopov <[email protected]> wrote: > > Hi all, > > Does anyone know whether and if at all there was an announcement that Go now > stack allocates objects with size < 32 bytes? I read the 1.25/1.24 Release > notes but if it is there I am missing something obvious. > > This questions is based on this talk from the last GopherCon: > > NL GopherCon 2025: Understanding Escape Analysis to Speed Up Your Code - Bill > Kennedy: https://www.youtube.com/watch?v=FUm0pfgWehI&t=974s > (16m15s): > > I believe it is Keith Randall answering - but the answer is that now values > smaller than 32 bytes are stack allocated (provided escape analysis agrees). > > There is also another reply from the room about why a particular value is > escaping. Any info on that would be helpful. > > Kind regards: > al_shopov -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/77C35050-7535-4D78-AD89-FA5A81C1FF29%40ardanlabs.com.
