3 ms·
See, the problem is that "message" is only used in this one place. In another place, I use there a type such as network, and the filters are entirely different
by kuschku 10y ago
See, the problem is that "message" is only used in this one place.
In another place, I use there a type such as network, and the filters are entirely different ones.
In yet another place, I use even other types.
The types used there have nothing in common, nor do the filters.
- cube2222 10y agoOk sorry, I thought the unit of generic'ness you mean is the message. You're basically just talking about generic custom collections. Yeah, it is a thing you won't get in Go. And you'll have to write it every time again. I'm usually just writing custom ones for each case, takes just a little bit more work. If I need more genericness, as I said, I use Java/Scala/F# EDIT: In theory you can hack this all together using interface{}, but I wouldn't do that, it's a hack and ignores the type safety of the language.