Комментарии:
A very good instruction in go generics. Well done buddy.. 🥇
ОтветитьThanks for your sharing!
ОтветитьIs 1.18 production ready? I am using 1.17 on my working project but it on early stage, I want to switch version to 1.18 but I'm scare of reliability. Thank you
ОтветитьI have to say, I doubt generics will make much of a difference in GoLang's popularity. GoLang is popular for a number of good reasons:
1. Unicode(utf-8) out of the box.
2. Simple to build.
3. Interfaces. i.e. a simple object model.
4. Concurrency.
5. Memory safety.
6. Higher order functions.
7. Code that's not cluttered with boiler plate. Very clean and standard source code bc of enforced standard formatting.
Generics might attract a few curious Java and C# programmers but I doubt they'll hang around long.
I almost forgot... Sane IO and slices.
Great video! Also, if you don't mind me asking, what is your IDE theme?
ОтветитьVery well explained. You're not only a golang Ninja ... but also a teaching Ninja. Thank you very muvh.
ОтветитьGeneric types or Generics 🙄
ОтветитьThanks for this. Really good content
ОтветитьNo front but I really can't understand why Go broke generics convention and used [ ] instead of <>. I don't care if <> is used in some other way but this looks unnatural and irritating for everyone coming from any other language. Many features differ between languages but for all languages I know generics are everywhere syntactically similar if not equal.
ОтветитьGreat content! Thanks for the channel!
ОтветитьDude... I sorta understand it as budding noobie-Golang-coder. But I have to re-watch it again when my knowledge and experience had matured. So Generics is how it handles, sorts any data types. Hmm... 🤔
ОтветитьSo are you ripping off "Let's Get Rusty" style or is he ripping off yours?
ОтветитьAre you going to update the cheat sheet with Generics?
Ответитьthanks for this video, it is quite clear 👍
Ответитьgo is inferior to rust
ОтветитьI'm learning go and all these new things are really exciting for me <3
Ответитьlong time not coding in go.. probably 5 years already.. is error handling any better? or is it still Nazi style error handling? god damn, they should introduce union type..
Ответить(edit)Actually after a week to work through some, not so cute examples I have found a very workable generic pattern that works for even complicated generic types.
Has anyone tried generics in Golang? I mean besides the cute examples! I can see this being the straw that broke the camel's back for some people trying GoLang. Talk about a half-assed approach to generics. Why would they produce such a terrible feature and then release it?
I used generics in Java, C#, C++, OCaml, and several other languages and I've never come across such an odd implementation of generics... I think they should have stuck without generics.
Great video!
Ответитьwe want more videos basic golang I'm from India waiting
Ответитьvery crisp and clear explanation of generics concept. thanks!
ОтветитьCool vid, thanks for the help
ОтветитьAfter this video I am officially moving from Typescript to Go.
Genetics are the necessity nowadays. Even the PHP crowd is waiting for them for a long time.
Excellent!
Hey, great explanation on generics, thank you! Are you planning another Video with generics in combination with Interfaces? Just asking for a friend… 😉😉
Ответитьis this dubbed in english?
ОтветитьGood explanation. Thank you for sharing your knowledge.
ОтветитьWhich environment are you using to dev? And which plugin allow look the var like it appear?
ОтветитьGoland vs VSC ?
Ответитьreally helpfull video! 只是,怪腔给怪调开门——怪到家了!
ОтветитьThis channel is exactly what I’ve been looking for; thank you
ОтветитьWhat about the "comparable" type ?
ОтветитьYou've just changed my mind about Generics in Go!
ОтветитьHow to add different generics to param 1 and 2
ОтветитьGoland is cool!@
ОтветитьIt was crystal clear. Thanks!
ОтветитьThis really helped me to understand how generics work in general - I always thought it to be some kind of a "higher level" thing, but it really is just a placeholder in a way, allowing generalizing functions, but also constrain the types the function works with.
ОтветитьAmazing video!
Ответитьtried to listen for three minutes, content is great, but the accent is terrible
Ответитьamazing explanation, ty
ОтветитьInsta sub - just for funny versions of go mascot.
ОтветитьExcellent video. Succinct and well organized. Thanks for this.
ОтветитьGreat tutorial overall! Why did your min(sf, 0.2) return 0.3 (incorrect) when the generic type was defined as ~float64? This problem did not exist when the generic type was defined using "type set". Is this another example of the compiler not being compatible with the latest language additions?
Ответитьthanks!
ОтветитьI'm beginner in Go, and I didn't know what generics is, but I heard everyone was looking forward to their releasing. Now I see and it looks like Go is losing it's tight types constraints and becomes TypeScript with their dope ANY, and everyone is happy about.... but it's awful, isn't it?
ОтветитьI wonder, is the future of all newer languages upgrading to the robustness of older languages? And we enjoy this "new" features 😅
ОтветитьWell kinda. You can't use them on struct methods which rules out about 60% of the use cases where I want to use generics.
ОтветитьThe inclusion of generics has made me more interested in the language because support for polymorphism is a pretty key tool in alot of codebases I work on. Why it took so long to implement Generics in GoLang is a mystery to me.
Ответитьthank you bro
Ответитьsomething I've recently done was needing to create a certificate generation function that could accept both RSA keys and EC keys, I did it slightly differently where it could accept any type and if it didn't mach a supported type it would error out. Now I should be able to go back and make it more strongly typed thanks to Generics
Ответить