3 ms·
I'm curious: Why don't people just use `new Object[]{arg1, arg2...}` ? It's one letter longer than `createArray(arg1, arg1...)`, doesn't require you to includ
by Groxx 16y ago
I'm curious: Why don't people just use `new Object[]{arg1, arg2...}` ?
It's one letter longer than `createArray(arg1, arg1...)`, doesn't require you to include that chunk of code, is infinite in length, and allows you to statically-type it in your type of choice. Heck, it's the same code, just removing a layer of indirection.
edit: noticed it's one character longer, not the same length. Maybe that's why?
- chrisbroadfoot 16y agoThis isn't regular code. This is code for the groovy runtime.
- Groxx 16y agoSo, why don't the Groovy runtime programmers just write `new Object[]{arg1, arg2...}` ?
- tedunangst 16y agoI suspect this is code meant to be called by generated bytecode, and generating the bytecode to call said function is easier than generating the bytecode to make a new object[]?
- wlievens 16y agoIt's been a while since I generated JVM bytecode (oh my, five years), but I don't recall there being array initializer instructions. In other words, the new Object[] {...} statement probably translates to a whole bunch of array-write operations on the caller side whereas with a method call you just push them all on the stack and invoke the utility method.