noalloc: Tooling and libraries to enforce zero heap allocations in Golang

Re:noalloc: Tooling and libraries to enforce zero heap alloc... by 80fj0348i on Saturday October 31, 2026 @10:04AM (#50316320)

Maybe the syntax is, but setting up the compiler and build system and linkers is very much not, especially for cross-compilation.

One of Go's major selling points is cross-compilation to other OSes and architectures is incredibly simple and fast, and _the same short build command works across every OS._

I maintain a CGO app that targets Windows macOS and multiple Linuxes and oh boy the build system is probably more complex than the app itself at this point.

[ Parent | on HN ]

Re:noalloc: Tooling and libraries to enforce zero heap alloc... by pjmlp on Saturday October 31, 2026 @06:33PM (#50320915)

I started coding with Timex 2068, developed for embedded in a past life, thus I fail to see how complicated doing a simple cross compiler in C happens to be.

I also have developed C and C++ native libraries for Tcl, Python, .NET, Java JVM/ART (JNI), Node.js.

[ Parent | on HN ]

Re:noalloc: Tooling and libraries to enforce zero heap alloc... by 80fj0348i on Sunday November 01, 2026 @08:57AM (#50325740)

Yeah I think this is a case of an old timer not having the perspective of the younger generation

`GOOS=windows go build ./...` versus all the jank you have to do with C is just not at all comaprable

[ Parent | on HN ]

Re:noalloc: Tooling and libraries to enforce zero heap alloc... by pjmlp on Monday November 02, 2026 @02:43AM (#50334133)

Try to do that for a Windows UWP, iOS, Android or z/OS application, in pure Go.

Yes it is super easy, in a few selected workflows of Linux, BSD, Windows, macOS, everything else is just as "complicated" as regular C cross compilation.

[ Parent | on HN ]

Re:noalloc: Tooling and libraries to enforce zero heap alloc... by 80fj0348i on Monday November 02, 2026 @02:08PM (#50341966)

Good thing I don't write code for those platforms! :P

[ Parent | on HN ]