thanks Francesc. clear explanation and learned a lot. Could you do episode about package, dependency management strategy for the relatively large project?
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)!
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.
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.
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!
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.
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?
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
The new.Hello func is calling old.Hello, so just dropping the old code at ruclips.net/video/Vg603e9C-Vg/видео.html 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?
+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
Your channel is one of the best things I ever found in internet. Thanks so much.
Thanks Francesc for your invaluable videos, an integral part of my continuous learning of this fantastic programming language.
What a great episode! You just did grind everything to the bits! Thanks.
thanks Francesc. clear explanation and learned a lot. Could you do episode about package, dependency management strategy for the relatively large project?
I was planning on doing an episode on dep ... maybe the time has come!
Awesome! thanks again for great work.
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)!
select a file in the root and then create the folder, no more moving around
Great episode, I get the same issues recording, I always find the second time is best. Really useful info too. Go aliases. Woo.
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.
glad you liked it! that was totally the goal of the episode :)
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.
I don't see how using an alias in this case would help over normal types.
Thanks Francesc, I learned learn a lot from your episodes, keep sharing.
I just found your channel. I really enjoy the videos, keep making them.
Another great episode! Thank you, Francesc.
thanks for watching!
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!
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.
Thank you for explaining this, otherwise I would have never understood the point.
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?
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
thank you so much
That got me too. Justforfunc should have thrown in a little aside to let viewers know about Stringer.
Why is it that you can print the celsius without calling `c.String()`?
Your VS Code looks beautiful, how can I setup like yours?
Just out of curiosity is there a way where I could find/print out all alias to a type?
Great Episode btw
I really enjoy the videos
I agree that Fahrenheit doesn’t make sense in general. Freezing is zero, period.
farenheit don't no make any sense to me :D hahaa
I promise you dude, as golang popularity grows this channel will escalate
Thanks for making these!
Instant like for Farenheits joke.
The new.Hello func is calling old.Hello, so just dropping the old code at ruclips.net/video/Vg603e9C-Vg/видео.html 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?
Am I the only one to think that there will be a lot of abuse regarding aliases which will obfuscate the code in end?
+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
I like the feature too, but I guess we will see what people will do with it.
>= 18, btw.
Great work, respect!
good example, thanks !!
Great Great episode,
Very usefull, thanks!
e dentical