Tree status for the Go 1.26 release and Go 1.27 development

[Michael Pratt]

Hi Gophers,

Go 1.26 will soon be scheduled for release (🎉!) and as described on https://go.dev/s/release, it's time to plan for Go 1.27 development. Tentatively, we expect a soft reopening (for fixes only, not new features yet) next week, and a full general tree reopening shortly thereafter. Please see the tracking issue 76474 for the latest tree status.

Please use this thread to discuss your own plans for the 1.27 development cycle and to coordinate submission.

(Reminder, this thread is for things you *PLAN TO DO YOURSELF*, not things you want other people to do.)

If you plan on working on potentially risky changes, please follow our guide in the wiki.

Thanks,
Michael for the Go team

[Russ Cox]

Hi all,

I am planning to land new, faster, simpler implementations of the innards of strconv.FormatFloat and strconv.ParseFloat. They should be extremely low risk since the visible behavior is unchanged.

Best,

Russ

[Ian Lance Taylor]

I hope to land the list of linker CLs starting from
https://go.dev/cl/723580. The overall goal is to (slightly) shrink Go
binary sizes.

I have some plans for speeding up determining function/file/line
numbers in stack tracebacks and the like, while using somewhat less
memory. But these are not yet implemented, so we'll see.

There is also room for shrinking funcdata tables if I get to it.

Ian

[Robert Griesemer]

I'll remove all the old machinery for Alias types handling in the type checkers since starting with 1.27 we'll only support explicit Alias nodes

(this will be announced in the release notes).

This should affect virtually no one except tool writers using the go/types API who are not yet setting Config.EnableAlias = true by default.

If this is you, now is the time to make the switch.

- gri

--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/golang-dev/CALoThU_WMUAcK6oAGqOf6JH-dJKFUf22m6qjeQBHUC1gu-KMjg%40mail.gmail.com.

[Russ Cox]

I am also planning to land Unicode 17 support. We got hung up on Unicode 15 for a while due to table changes in Unicode 16 that our code couldn't cope with, but I have pending CLs that revise the code so that we can successfully update to Unicode 17 (the latest version). Unicode 18 isn't planned until September, so Go 1.27 will be up-to-date as long as we get 17 in.

Best,

Russ