justforfunc #18: understanding Go's type aliases

[@marksaravi7160]

Your channel is one of the best things I ever found in internet. Thanks so much.

[@AlexanderDemin]

What a great episode! You just did grind everything to the bits! Thanks.

[@paulyeoh4266]

Thanks Francesc for your invaluable videos, an integral part of my continuous learning of this fantastic programming language.

[@theyruinedyoutubeagain]

19:30 I have the same damn issue with vscode xD Always have to move shit around after I create it. I absolutely love it though, and credit you fully for making me switch to it. Good episode by the way (as always)!

[@IvanPortoCarreroBE]

select a file in the root and then create the folder, no more moving around

[@meowmeow70]

thanks Francesc. clear explanation and learned a lot. Could you do episode about package, dependency management strategy for the relatively large project?

[@JustForFunc]

I was planning on doing an episode on dep ... maybe the time has come!

[@meowmeow70]

Awesome! thanks again for great work.

[@mybigbeak]

Great episode, I get the same issues recording, I always find the second time is best. Really useful info too. Go aliases. Woo.

[@AnthonySBD]

good episode, i wasn't sure how or why id bother to ever use type aliases besides packages changing location / name and this video actually gave me some useful scenarios where it can come in handy.

[@JustForFunc]

glad you liked it! that was totally the goal of the episode :)

[@alesresta]

Another great episode! Thank you, Francesc.

[@JustForFunc]

thanks for watching!

[@nexdev09]

I just found your channel. I really enjoy the videos, keep making them.

[@Cutiepie-ky9oh]

Why is it that you can print the celsius without calling `c.String()`?

[@dksingh04]

Thanks Francesc, I learned learn a lot from your episodes, keep sharing.

[@pmareke]

In the minute 30:55 you finally move the code from the old to the new package but I can't see the difference from it and moving forward without the alias feature. I mean I'm lost because I don't see the benefits or even the possible problems, why you can't move code directly from one package to another via copy-paste? Thanks for your videos by the way, are amazing!

[@danielscholz613]

It think the trick is that you only want to make changes in one package at a time in terms of continuous integration as he mentioned at some point earlier.

[@theearthboundkid]

For channels, I often end up naming a type, just so I can pass groups of things into and out of the channel more easily. With type aliases, it could make more sense to use type chanResults = struct { int; err } or whatever, so that you aren't locking yourself down to one type implementation.

[@JustForFunc]

I don't see how using an alias in this case would help over normal types.

[@johnbalvin5401]

I dont get why at 2:22 it prints "10.00 C", wouldnt be the code for that at line line 13 like "fmt.Println(c.String())" because thats how you call a method?

[@valdeleplace4536]

Method String is "special" because it makes your type implement fmt.Stringer, so implicitly the String method will be called by fmt.Println. See golang.org/pkg/fmt/#Stringer

[@johnbalvin5401]

thank you so much

[@bhfaught]

That got me too. Justforfunc should have thrown in a little aside to let viewers know about Stringer.

[@blondie9990]

Thank you for explaining this, otherwise I would have never understood the point.

[@kitgary]

Your VS Code looks beautiful, how can I setup like yours?

[@alaypatel7511]

Just out of curiosity is there a way where I could find/print out all alias to a type? Great Episode btw

[@buscoopwang8874]

I really enjoy the videos

[@aaronprindle385]

Thanks for making these!

[@dansplain2393]

I agree that Fahrenheit doesn’t make sense in general. Freezing is zero, period.

[@swileniwanow8089]

I promise you dude, as golang popularity grows this channel will escalate

[@niranjangodbole8784]

farenheit don't no make any sense to me :D hahaa

[@belekabylov]

Instant like for Farenheits joke.

[@13TheGUNNER]

good example, thanks !!

[@greiezer]

The new.Hello func is calling old.Hello, so just dropping the old code at kzbin.info/www/bejne/jJiZYWabbqhgjMk will break the CI-build since we did not copy the old implementation over to new.Hello and remove the call to old.Hello, or did I get that wrong?

[@easternsunking255]

Great Great episode,

[@rraulinio]

>= 18, btw. Great work, respect!

[@DJjetseb]

Am I the only one to think that there will be a lot of abuse regarding aliases which will obfuscate the code in end?

[@JustForFunc]

+Just AGuy I think there's a risk people might try to obfuscate code, but that risk exists pretty much with every feature, and the benefits of type aliases are worth it imo

[@DJjetseb]

I like the feature too, but I guess we will see what people will do with it.

[@MrSnack111]

Very usefull, thanks!

[@andherium]

e dentical