Never use a dependency that you could replace with an afternoon of programming

Re:Never use a dependency that you could replace with an aft... by microcolonel on Tuesday August 11, 2020 @03:57PM (#24125233)

What magic would enable that? I don't think the VM is likely to cache a string of 6 spaces, it has no way of knowing that would be a common parameter, and no heuristic to determine that it's likely.

It may specialize or inline, but that's a separate matter.

P.S. I think there's a bug here.

[ Parent | on HN ]

Re:Never use a dependency that you could replace with an aft... by cogman10 on Tuesday August 11, 2020 @04:10PM (#24125395)

JIT is the magic sauce and this a pretty regular optimization.

    Step 1, inline repeat.
    Step 2, remove the intermediate array allocation
    Step 3, allocated a string array sized for the pad + str
    Step 4, Use one of the many CPU instructions to repeatably copy the padding character and then the `str` into the same array of characters.

None of these optimization would be out of the question for the Jit (and I'd expect them). You don't need the cache at all, it's just a waste. The only thing it saves it creating the intermediate string which is HIGHLY likely to be optimized away with the simple code.

[ Parent | on HN ]