Go 1.17 is deprecating the traditional use of 'go get'

Re:Go 1.17 is deprecating the traditional use of 'go get' by kazinator on Friday June 25, 2021 @01:21PM (#27633717)

You can't always easily compile an old C program against the new C libraries you are running. Even if you can compile it, changes in libraries can break programs. E.g. say in the ancient library, memcpy with null pointer parameters worked, if the size was zero. The new library checks it and aborts. There are all sorts of issues like this.

Every time libraries and compilers advance, you're effectively porting all the existing code. You have to fix any build breakage, and re-validate everything.

Moreover, Python is a C program. Just get the old Python 2 C code and compile it against "the same version of libc you're running" and it will work, right? Where is the problem?

[ Parent | on HN ]

Re:Go 1.17 is deprecating the traditional use of 'go get' by josefx on Friday June 25, 2021 @02:30PM (#27634586)

Why recompile it when the existing binary still works with the current runtime? At least on Linux the old version of memcpy will still be included in the runtime library to avoid this kind of issue.

[ Parent | on HN ]