Exploring Go 1.22: Unveiling New Features and Anticipating Exciting Changes

[@johnr3936]

Great video, looking forward to your coverage on future releases.

[@peterszarvas94]

wildcard matching makes using a framework like echo or gin kind of unnecessary. the less dependency the better

[@sebastianswc]

grreat video, thank you!

[@sarmhn123]

Thanks mate

[@Snailsxd]

7:47 honestly I'm not sure I like this, what if for some reason I still need the old slice, now I'd have to create a copy, I don't see why that function should mutate the original slice if it returns a new one

[@codeandlearnwithlove]

The functions that we are talking about modify the original slice and do not return a new slice. So, if you need the old slice you would have to maintain a copy even with the current versions of these functions. Please check the Delete function for example pkg.go.dev/slices#Delete The reason for zeroing the elements between the new length and the old length lies in this statement of the existing function: "If those elements contain pointers you might consider zeroing those elements so that objects they reference can be garbage collected." I hope it makes more sense now 🙂

[@Snailsxd]

​@@codeandlearnwithlove The zeroing of the elements for garbage collection makes sense.

[@MosiurRahman-dl5ts]

I am the 650th subscriber

[@dekooks1543]

Hey 👋 Can I ask what tool you used to make this presentation?

[@codeandlearnwithlove]

Hi, nothing too fancy just Google Slides 😄

[@eser-sahin]

Great channel, please continue. By the way, your discord link is broken.

[@codeandlearnwithlove]

Thanks a lot! Discord link should be fixed now :)

[@EightSixx]

nuice!

[@bebobauomy1265]

The for loops are already slow, that will make them more slower.

[@codeandlearnwithlove]

It was released as an experimental feature in the previous version. So I am sure the Go team would have made sure that there are no performance hits due to it, but it will be good to benchmark and see.

[@pookiepats]

Guys, if you want anything you say to be taken seriously you have to get the basics of grammar right; “more slower” is an abomination.

[@bebobauomy1265]

@@pookiepats Sorry, English is not my native language.

[@codeandlearnwithlove]

@@bebobauomy1265 Hey don't be sorry and please ignore the comment. The focus of this video is Go, not English 🙂

[@infastin3795]

No, it won't. Did you really think that developers would've made such a change if there was a major performance drawback? In cases where you are not referencing variables performance will be the same due to compiler optimization. In opposite cases there also won't be any performance difference since before this change you would create a new variable inside a loop anyway.

[@user-oq2vq9co7e]

Sir will you make a rest api series using go

[@codeandlearnwithlove]

Yes, I will 🙂 just want to cover all the required topics first.

[@oriontvv]

it is a python's victory, lol)