Russ Cox

Now that math/rand defaults to a pre-seeded random generator, this is not an API change and does not need to be a proposal. (Of course, any implementation needs to respect...

**Removed from the [proposal process](https://go.dev/s/proposal)**. This was determined not to be a “significant change to the language, libraries, or tools” or otherwise of significant importance or interest to the broader...

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

It would be very helpful to know how much code this will affect. Despite the dire warnings in the commentary right now, there are compiler special cases (which we can't...

Per https://github.com/golang/go/wiki/Deprecated we cannot add deprecated notices until Go 1.22. I'd still like to know more about how much code this will flag.

I downloaded the latest release and prerelease version of each module known to proxy.golang.org (using index.golang.org's list) as of a few weeks ago. Grepping for StringHeader or SliceHeader in that...

It still seems like we don't know the full impact, but we do know that much code using these is incorrect, and there are much better alternatives now, so marking...

Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group

Re https://github.com/golang/go/issues/56906#issuecomment-1414440862, you're right that we don't know the impact. I addressed that in https://github.com/golang/go/issues/56906#issuecomment-1404038635: > It still seems like we don't know the full impact, but we do know...

No change in consensus, so **[accepted](https://go.dev/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group