3 ms·
Me too. We have around a dozen go services and I have maybe used or seen interface{} once or twice for a hack. Especially after generics. I think the parent com
by coffeebeqn 3y ago
Me too. We have around a dozen go services and I have maybe used or seen interface{} once or twice for a hack. Especially after generics. I think the parent comment is suffering from poor quality go code. It’s like complaining about typescript because things in your codebase don’t have types
- xarope 3y agoDealing with databases and data scanning into custom structs, you would be writing lots Scanner/Valuer custom functions which use interface{} If you are the lucky ones not dealing with databases, I sort-of envy you...!
- kiitos 3y agoApplications should basically never need to write custom Scanner/Valuer functions that deal in interface{}, if you find yourself doing that it's a red flag
- badrequest 3y agoI use sqlc and it makes this a non-issue.