News for hackers. Stuff that matters.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by rat9988 on Friday May 27, 2022 @04:31AM (#31527324)
My old go code doesn't compile anymore with the newer compiler versions
Re:Today’s JavaScript, from an outsider’s perspective (2020) by synthmeat on Friday May 27, 2022 @04:37AM (#31527351)
What was it that broke it? Usage of unsafe? Security and bug fixes in the compiler/tooling? Just interested.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by jcalabro on Friday May 27, 2022 @11:15AM (#31530564)
The Go 1 promise[0] says that the language spec and set of core libraries will be backwards compatible. I maintain a few dozen go projects, some of which are 10 years old, and while upgrading from i.e. 1.4 -> 1.18 has been relatively easy, it definitely has not been zero work. There are changes in the tooling, dependency ecosystem, deprecated dependencies that should be replaced, runtime behavior differences, things like that. But the language itself and stdlib is totally stable.

[0] https://go.dev/doc/go1compat

Re:Today’s JavaScript, from an outsider’s perspective (2020) by rat9988 on Friday May 27, 2022 @06:15AM (#31527871)
I didn't try for a long time I have a hard time remembering. I believe it had something to do about how it handles dependencies.