This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Go · Archive · Week 38 · Sep 14 – 20, 2026

syscall: update Windows SysProcAttr for recent process creation features

Worth knowingstdlib

What changed
The proposal adds several fields to syscall.SysProcAttr on Windows: Jobs []Handle, Console Handle, Desktop string, AppContainer *AppContainer, and Sandbox *Sandbox. It also introduces new types AppContainer and Sandbox that wrap Windows security and sandbox structures.
Production impact
The source does not say.
Try it
In a Windows build, inspect the syscall.SysProcAttr struct to see the new fields.
Source
github.com/golang/go/issues/80415

Understand it, then run it

Run it now

Todaygo
// This program demonstrates that the new fields are not yet available in Go 1.27.1.
// It simply imports syscall, uses the existing SysProcAttr type, and prints its zero value.
// The output shows the struct with no custom fields, confirming the current API state.
package main

import (
	"fmt"
	"syscall"
)

func main() {
	// Create a zero-valued SysProcAttr and print it.
	// The struct contains only the fields that are currently defined in Go 1.27.1.
	var attr syscall.SysProcAttr
	fmt.Printf("Current SysProcAttr: %+v\n", attr)
}

What it printed when we ran it on Go 1.27.1

Current SysProcAttr: {Chroot: Credential:<nil> Ptrace:false Setsid:false Setpgid:false Setctty:false Noctty:false Ctty:0 Foreground:false Pgid:0 Pdeathsig:signal 0 Cloneflags:0 Unshareflags:0 UidMappings:[] GidMappings:[] GidMappingsEnableSetgroups:false AmbientCaps:[] UseCgroupFD:false CgroupFD:0 PidFD:<nil>}

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.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed