News for hackers. Stuff that matters.

A comment on Go 1.17 is deprecating the traditional use of 'go get'. Parent comment

Re:Go 1.17 is deprecating the traditional use of 'go get' by marcosdumay on Friday June 25, 2021 @01:16PM (#27633633)
> What's the alternative?

Have an import switch that enables a legacy mode, that will convert your strings into and out of the library? You can even require that the application developers cast their strings into the correct ones if you don't want to calculate it on the compiler.

[ Parent | on HN ]
Re:Go 1.17 is deprecating the traditional use of 'go get' by kortex on Friday June 25, 2021 @03:06PM (#27634976)
That's just not possible with python's computational model. That works for "from future import print" cause that's just an additional function.

str is too deeply embedded and used in too many dynamic and unique ways for that approach to work without doing some really ugly or nonperformant or community-fracturing things.

[ Parent | on HN ]