3 ms·
It's ruby, so the expected complexity of any line of code is "it might complete sometime in my lifetime". No surprises for users here, which is why that bug la
by TheDong 10y ago
It's ruby, so the expected complexity of any line of code is "it might complete sometime in my lifetime".
No surprises for users here, which is why that bug lasted for about 4 years with noone caring.
If the documentation stated it was O(n), or benchmarks tested it was fast, then it being slow would become a bug.
As is, it's just what it is.
- aetherson 10y agoWell, probably the reason it lasted for about 4 years with no one caring is because .reject! is a fairly rarely used function.