News for hackers. Stuff that matters.
Re:Go 1.17 Release Candidate 1 by verdverm on Tuesday July 13, 2021 @06:32PM (#27827064)
https://golang.org/doc/go1compat

Generally, adding features does not break backwards compatibility. Note that ioutil was depreciated while it is unlikely to ever be removed

Re:Go 1.17 Release Candidate 1 by 37ef_ced3 on Tuesday July 13, 2021 @06:59PM (#27827271)
"The io/ioutil package has turned out to be a poorly defined and hard to understand collection of things. All functionality provided by the package has been moved to other packages. The io/ioutil package remains and will continue to work as before, but we encourage new code to use the new definitions in the io and os packages."

It will never be removed, thankfully.

Re:Go 1.17 Release Candidate 1 by nine_k on Tuesday July 13, 2021 @11:45PM (#27829476)
Even if the new stdlib is 100% backwards compatible (which I think is the goal), it still needs rework to make it use generics where appropriate.
Re:Go 1.17 Release Candidate 1 by verdverm on Wednesday July 14, 2021 @08:56AM (#27832490)
why does the stdlib need to adopt generics? That would break the Go1 promise. They would likely introduce new functions rather than changing existing ones. RE: what they did with the ioutil package