How Go 1.22 fixed an issue that caused Google problems

[@tariik.h]

The correct way of addressing the issue is not to redeclare the variable, but to use func(v string) instead of func().
func() uses a pointer implicitly, whereas func(v string) copies the value.
If we use func(), the value might be modified by some other part of the program.

[@pasokoner]

What is that extension, that let you see the type of variable in a loop.

[@abiodun6897]

thanks , i recently go into go again after some years had no idea this was fix , btw whats you editor config

[@FloWoelki]

awesome stuff!
generally, I use Zed at the moment as my main editor. so, I was switching from nvim to Zed. but the editor theme is the official GitHub theme.

[@abiodun6897]

@@FloWoelki thank you 👍🏽

[@ayushtripathi4514]

can you please create a video on you developer workflow? Editor config etc

[@FloWoelki]

Sure, it's in the pipeline :)

[@ayushtripathi4514]

@@FloWoelki awesome. Recently found your channel, already loving the content. ❤️

[@FloWoelki]

@@ayushtripathi4514 Much appreciated, thank you! :)

[@l_ukas]

Isn't this a huge breaking change for existing software?

[@FloWoelki]

Not really, because the original code itself did not really change. The only change was in the Go compiler itself.

[@mikeafter5]

Thanks.

[@FloWoelki]

You're welcome :)