6 ms·
There's nothing stopping you from building bad abstractions in Go, and I find it pretty common. Here's an example: Debug(msg string, keyvals ...interface{}) T
by eweise 4y ago
There's nothing stopping you from building bad abstractions in Go, and I find it pretty common. Here's an example:
Debug(msg string, keyvals ...interface{})
The keyvals interface assumes you are passing in both a key and a value but if you don't, it doesn't work correctly and in fact in our code I think it blows up.
- philosopher1234 4y agoDefinitely. Go is not the last word in the conversation on programming language design, and it hasn’t solved the problem of prohibiting harmful abstractions. But I do think the conservativeness around abstraction is an improvement, at least culturally, over the way many language communities view software development.