Been coding for 5+ years professionally and used generics once or twice in my entire career. Is one of those things that solves a very niche problem and not everyone needs or cares for generics. Probably library writers are the ones that uses them the most if I was to guess.
For Generics, workspaces, fuzzing, etc., just don't have a need for them. For new features, I would like to see some memory optimizations similar to Rust. I hate... Rust syntax. I do think it would be wise for Go parser to know that if variables are no longer used past a point, then go ahead and destroy them. I know Go tries to put as much as it can on the stack, but that is at the function level.
Feedback on generics: My previous languages don't have generics, so I haven't "learned to need" them. The very few cases I think I could use them, turned out that I can't due to current limitations. i think these were input arguments in methods. Looking up the syntax for this doesn't help either. What I'd like to see in Go, and pointed out when filling the survey, is to have some kind of immutability and better/actual enums. However, knowing their resistance to add anything to the language + only 5% in survey, I don't see it happening.
Get your *FREE Golang Cheat Sheet* -
golangdojo.com/cheatsheet
Been coding for 5+ years professionally and used generics once or twice in my entire career. Is one of those things that solves a very niche problem and not everyone needs or cares for generics. Probably library writers are the ones that uses them the most if I was to guess.
For Generics, workspaces, fuzzing, etc., just don't have a need for them. For new features, I would like to see some memory optimizations similar to Rust. I hate... Rust syntax. I do think it would be wise for Go parser to know that if variables are no longer used past a point, then go ahead and destroy them. I know Go tries to put as much as it can on the stack, but that is at the function level.
Feedback on generics: My previous languages don't have generics, so I haven't "learned to need" them. The very few cases I think I could use them, turned out that I can't due to current limitations. i think these were input arguments in methods. Looking up the syntax for this doesn't help either.
What I'd like to see in Go, and pointed out when filling the survey, is to have some kind of immutability and better/actual enums. However, knowing their resistance to add anything to the language + only 5% in survey, I don't see it happening.
Thanks wallace 👍
Thanks bro
Can you do tutorials about pocketbase and how to expand it 🙂
no yoooo