3 ms·
You gave a completely unrealistic example, no one is passing around Object varargs. In the off chance, just specify the type.. I gave a more realistic example
by kaba0 3y ago
You gave a completely unrealistic example, no one is passing around Object varargs. In the off chance, just specify the type..
I gave a more realistic example where you actually make use of your objects
- iraqmtpizza 3y agoFirstly, I gave two examples. Your argument to the first one is "nuh-uh" (summarized). Your argument to the second one is nonexistent. Secondly, it's not unrealistic. It's not even realistic. It's real. R-E-A-L real. It's in production systems right now, as I said. Modern startups. If you think you can design it better, by all means. "Put up or shut up" is the phrase, I think. Thirdly, any time you have an API that accepts a supertype of the instance in question, this will happen. Run away and hide from the truth. Or man up and admit you oversold your incorrect theory of var. Fourthly, you didn't even address the readability issue. Which of course you wouldn't because... var. Like literally VAR. lol. Fifthly, you still haven't come up with an answer as to what I misunderstood, specifically. Sad!