3 ms·
Go’s decision to not support function overloading leads to a tonne of really ugly APIs. Obviously every decision in language design is a tradeoff, but IMO they
by yashap 3y ago
Go’s decision to not support function overloading leads to a tonne of really ugly APIs. Obviously every decision in language design is a tradeoff, but IMO they made the wrong call here.
- philosopher1234 3y agoI'm not sure how I feel about this. What are the actual consequences of these apis being "ugly"? Like, why does that matter?
- numbsafari 3y agoTo me, at least, it is like listening to a person who constantly says "uh..." while talking. Occasionally, sure fine. But it's so pervasive in commonly used APIs that it becomes annoying. Let's be clear: this is just a peeve of mine.