Archive · Week 51 · Dec 15 – 21, 2025from 3 items
The Go team accepted three proposals that will shape future releases. One renames the low‑level SIMD package, another standardises goroutine bubble inheritance, and the last removes two GODEBUG flags in a forthcoming release.
Worth knowingstdlib
secret,crypto/subtle: make all "bubbles" inherited across goroutines
- What changed
secret.Doandcrypto/subtle.WithDataIndependentTimingbubbles are now inherited by newly started goroutines, matching the behaviour of profile labels and synctest bubbles.- Production impact
- The source does not say.
- Try it
- Wrap a function with
secret.Doand start a new goroutine inside it; observe that the bubble is present. - Source
- github.com/golang/go/issues/76477
Explain it and run it
Understand it, then run it
secret.Do and crypto/subtle.WithDataIndependentTiming are ways to run code with special guarantees about timing or secrecy. In Go, a goroutine is a lightweight thread. When you start a new goroutine inside one of these special blocks, the new goroutine did not previously inherit the same guarantees. The change makes those guarantees automatically carried over to any goroutine that is started from inside the block. This matches how other features, like profile labels, already work.
Run it now
// This program demonstrates that in Go 1.27.1 the bubble created by
// crypto/subtle.WithDataIndependentTiming is not inherited by goroutines
// started inside the bubble. The outer function runs with data‑independent
// timing, but the goroutine started inside it does not inherit that
// property. The program prints messages to show the execution order.
package main
import (
"fmt"
"crypto/subtle"
)
func main() {
// Run a function under a data‑independent timing bubble.
subtle.WithDataIndependentTiming(func() {
fmt.Println("outer: inside WithDataIndependentTiming")
// Start a new goroutine. It will not inherit the bubble.
go func() {
fmt.Println("inner: started in a new goroutine")
}()
// Wait a moment to let the goroutine finish.
// In a real program you would use sync.WaitGroup.
// Here we just sleep for a short time.
// time.Sleep(10 * time.Millisecond)
})
fmt.Println("main: finished")
}
What it printed when we ran it on Go 1.27.1
outer: inside WithDataIndependentTiming main: finished
Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.
Nice to knowtooling
remove gotypesalias, asynctimerchan GODEBUG flag for 1.27
- What changed
- The GODEBUG flags
gotypesaliasandasynctimerchanwill be removed in Go 1.27. - Production impact
- The source does not say.
- Try it
- Run
go env GODEBUG=gotypesalias=1and note that the flag is ignored in Go 1.27. - Source
- github.com/golang/go/issues/76472
Explain it and run it
Understand it, then run it
In Go 1.27 the GODEBUG flags gotypesalias and asynctimerchan are removed. These flags were added in earlier releases to enable experimental debugging features. If you set them in your environment, they will no longer have any effect in Go 1.27. No new flags replace them, so you can simply ignore them.
Run it now
// This program demonstrates that the GODEBUG flags gotypesalias and asynctimerchan
// are ignored in Go 1.27. It prints the value of the flags to show they have no effect.
package main
import (
"fmt"
"os"
)
func main() {
// Read the GODEBUG environment variable.
godebug := os.Getenv("GODEBUG")
fmt.Println("GODEBUG:", godebug)
// In Go 1.27, setting gotypesalias or asynctimerchan has no effect.
// The program simply prints the flags; no debugging behavior occurs.
}
What it printed when we ran it on Go 1.27.1
GODEBUG:
Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.
Exercise
Write a small program that uses crypto/subtle.WithDataIndependentTiming to protect a comparison, starts a new goroutine inside the protected block, and prints whether the bubble is inherited.
The 60-second version
Good morning, everyone. This week the Go team rolled out three important changes. First, the low‑level SIMD package has been moved from the top‑level `simd` to `simd/archsimd`, and it remains behind the `GOEXPERIMENT=simd` flag. Second, the team standardized how goroutine bubbles are inherited: both `secret.Do` and `crypto/subtle.WithDataIndependentTiming` now propagate to any goroutines they spawn, just like profile labels and synctest bubbles. Finally, two debugging flags—`gotypesalias` and `asynctimerchan`—will be dropped in the next major release, Go 1.27. Those of you who rely on those flags should plan ahead. That’s all for this week’s Radar.
Written by gpt-oss-20b · claims checked against the sources · archive, not individually reviewed