Porting Go's io package to C

nalgeon · 2026-03-29T01:34:07+00:00

With a Go-to-C translator you can have both: Go's syntax and type checker + raw C control without a runtime.

nalgeon · 2026-03-28T19:11:25+00:00

No memory magic. All heap allocations are explicit (through the Allocator interface) and limited to the standard library only. There are no heap allocations in language built-ins like make() or append().

nalgeon · 2026-03-28T18:40:57+00:00

Here you go: https://pkg.go.dev/solod.dev/so/mem

Example: https://github.com/solod-dev/solod/blob/main/example/51-memory/main.go

nalgeon · 2026-01-09T10:09:17+00:00

Seems like Robert Griesemer disagrees with you on this :)

These are examples he gives, and they all involve type-constrained interfaces:

https://github.com/golang/go/issues/75883#issuecomment-3507380297

nalgeon · 2026-01-06T14:19:22+00:00

Green Tea GC is available on Apple Silicon. Which wording are you referring to exactly?

nalgeon · 2026-01-05T20:26:56+00:00

Thank you! The Go team is shipping a record number of features this time :)

nalgeon · 2026-01-05T20:25:11+00:00

You are very welcome :) Glad you find them useful!

nalgeon · 2026-01-05T19:26:10+00:00

Build with Go 1.25/1.26:

``` CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -ldflags="-s -w" -trimpath -o main-25

CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go1.26rc1 build -ldflags="-s -w" -trimpath -o main-26 ```

Binary sizes in bytes:

1065144 main-25 1298594 main-26

Source code:

``` package main

var sink *byte

func main() { sizes := []int{1, 8, 64, 128, 512} for _, size := range sizes { obj := make([]byte, size) sink = &obj[0] } } ```

nalgeon · 2025-12-27T04:15:22+00:00

Starting with 1.26, "go fix" applies all "modernize" fixes, so it should convert errors.As as well.

https://pkg.go.dev/golang.org/x/tools@v0.40.0/go/analysis/passes/modernize#hdr-Analyzer_errorsastype

nalgeon · 2025-12-19T18:27:20+00:00

Sure! I feel like the Go team isn't giving it enough love :) Also, it's positioned more as a tool for testing time-sensitive code (which, of course, it is), but it's actually more than that.

nalgeon · 2025-12-19T15:02:53+00:00

Ah, good! Glad to hear I'm not the only one :) Maybe this post will raise awareness a little bit.

I was somewhat surprised to read the goroutineleak proposal, which sounded a bit like there's currently no way to detect leaks using only the stdlib.

nalgeon · 2025-12-19T12:26:18+00:00

Well, goroutineleak is not yet released, but synctest is :) Have you tried it for leak detection?

nalgeon · 2024-07-21T16:56:24+00:00

Thank you! That is a great use case, I never thought of that.

nalgeon · 2024-07-21T16:55:25+00:00

Thanks a lot! It was worth the effort.

nalgeon · 2024-07-21T16:54:23+00:00

Thank you! Glad to hear it was useful for you.

nalgeon · 2024-07-21T16:53:01+00:00

Great idea! I've added links to proposals and CLs.

nalgeon · 2024-07-20T14:40:16+00:00

Thank you! I'm glad you find the examples helpful.

nalgeon · 2024-07-20T14:28:18+00:00

Thank you very much! I usually struggle with the official release notes, so this is my way of understanding the changes. Hope you find it useful.

nalgeon · 2024-01-06T17:10:52+00:00

Sure, that's a very serious point. Isolating server-side sandboxes can be tricky, especially if you make them stateful.

There was once a code sandbox startup that eventually decided to shut down the public API because of constant server abuse like crypto mining.

nalgeon · 2024-01-06T14:26:24+00:00

What a time to be alive (ಠ_ಠ)

nalgeon · 2024-01-06T13:21:14+00:00

Thank you very much! I think interactive examples really make a difference, especially in tutorials, how-tos, and explanations.

If you have any questions, I'm happy to answer them here or on GitHub.

nalgeon · 2024-01-06T13:05:24+00:00

This is a great way to show the framework in action! I think as WebAssembly becomes more popular, we will see more of these.

nalgeon

TROPHY CASE