Level Up Your Golang: 5 Concepts You Need to know

[@CrayonEater9845]

I've been writing Go for a month, but have 5 years in industry. These are all pretty basic concepts in Go. Also don't use goto. It destroys control flow and there are other ways to do what it enables. If you look at C, goto exists, but you really only see its use when taking emergency recovery actions like in the Linux kernel.

[@FloWoelki]

I agree with you, but it's definitely good to know the concepts. Sure, they do destroy in some way the control flow, but when used correctly, they can simplify things a lot and make your code even more readable and maintainable. Even the official standard library uses `goto`.

[@DavidSmith-ef4eh]

c# implementation of LINQ and some of their other features use goto. I assume there is a usecase for everything, its' just discouraged since people would abuse it.

[@grouponsurgeon]

You might not have set out to explain bit shifting but you did a pretty good job of simplifying the concept

[@FloWoelki]

Thank you :) I might make a video about bit shifting in the future.

[@adanpalma4026]

For me go to is label break just for bring some clarity. Because goto outherloop is better that just break

[@a_maxed_out_handle_of_30_chars]

simple and to the point, thank you :)

[@FloWoelki]

Glad it helped! :)

[@matthew1106]

More videos like this please!

[@FloWoelki]

Sure, I'll try my best!

[@cariyaputta]

Nice golang focused videos, added to my library.

[@FloWoelki]

That's awesome, thank you :)

[@sehbazrafik]

amazing video, can you please have your dev setup on the laptop + desk tour video.

[@KanishkaDilshan]

Great content!

[@FloWoelki]

Thank you so much! :)

[@esra_erimez]

"Go To Statement Considered Harmful" -Edsger Dijkstra

[@adanpalma4026]

😂 please. That was said in a context totallundiferent where go to was used indicriminated as in basic where you can jump to anywhwere in the code. This is no the case

[@thewalkthroughmaking]

From now on I'm going to start quoting "This is somehow a problem, cuz it's not really beautiful and it is really really ugly" daily hahahaha

[@FloWoelki]

That's the spirit :D

[@MattRobinsonDev]

great stuff

[@FloWoelki]

Thank you :)

[@李伟鸣]

good stuff!

[@FloWoelki]

Thank you :)

[@lemurza5236]

Generally speaking you should avoid labels. They are one of the features of Go that hurt the language in a big way. Labels and Goto are horrible and should be avoided at all costs

[@FloWoelki]

I agree, generally speaking you should avoid these, especially for simple flows. However, they do exist for a reason, and even the standard library of Golang uses both concepts. Obviously, they should be used judiciously. But, especially for things like simplifying error handling and cleanup code (in some cases) can lead to more readable and maintainable code.

[@adanpalma4026]

@@FloWoelkiyes that is the point. Its like a go sub or call func in long infinite chain call. Like call func1 and in func1 call func 2 and son on. In this case we are dividing and specialiating code but in a bad way of control. Is the same with labels in go. If you use in a propper way no problem. People are afraid of goto because of basic where you can go to anywhere in the code but labels in go are fantastic tool

[@justinjustin4605]

what theme is that?

[@FloWoelki]

It's the GitHub theme :)

[@richardbolanos50]

When it comes to the new keyword what is the difference between return new(Counter) and return &Counter{} if any. Is there a performance benefit by any chance

[@loo_9]

there should not be a performance difference, but the only way to truly know this is benchmarking. the compiler would recognize that the memory escapes the function scope so it has to be heap allocated. the only difference is that {} you can specify initial values

[@FloWoelki]

I agree; there shouldn't be any performance difference because the Go compiler optimizes both expressions similarly. I think this is a valuable discussion: groups.google.com/g/golang-nuts/c/GDXFDJgKKSs

[@richardbolanos50]

@loo_9 and @FloWoelki thanks for taking the time to reply.

[@ArthurSchoppenweghauer]

iota is a greek word and is pronouced iota.