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 8 · Feb 16 – 22, 2026

x/net/http2: deprecate WriteScheduler

Worth knowingstdlib

What changed
The x/net/http2.WriteScheduler interface and its implementations are marked deprecated. The round‑robin scheduler remains the default; the priority scheduler is buggy and will not be fixed.
Production impact
The source does not say.
Try it
Run go list -deps golang.org/x/net/http2 and look for WriteScheduler in the documentation.
Source
github.com/golang/go/issues/67817

Understand it, then run it

The x/net/http2.WriteScheduler interface lets a server decide the order in which data is sent on HTTP/2 streams. Three built‑in schedulers exist: round‑robin (the default), random, and priority. The priority scheduler is buggy and the HTTP/2 prioritization it implements is no longer supported. Because of that, the Go project has marked the whole WriteScheduler mechanism as deprecated. The round‑robin scheduler will remain the default, and the priority scheduler will not be fixed.

Run it now

Todaygo
// This program demonstrates that the `x/net/http2.WriteScheduler` interface
// is still part of the external `golang.org/x/net/http2` package and is
// marked deprecated. Since the sandbox has no network access, we cannot
// import that package, so we simply print a message explaining the
// situation.

package main

import "fmt"

func main() {
	fmt.Println("The WriteScheduler interface in golang.org/x/net/http2 is deprecated.")
}

What it printed when we ran it on Go 1.27.1

The WriteScheduler interface in golang.org/x/net/http2 is deprecated.

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