Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I have heard that replacing for loops with repeated commands is sometimes more efficient, but I don't think that was the reason here, especially for 18000 iterations.
-
hack64563y"18000 duplicated lines that were manually copy pasted by a monkey"
Here, I fixed your typo. -
@iiii yup, and its been pretty useless for the last 20+ years, atleast in compiled languages as any sane compiler does it for you when it is beneficial. (i.e whenever unwinding won't cause you to flood the l1 cache)
-
iiii92263y@ItsNotMyFault depends, I guess. Compilers are smart indeed, but still not totally smarter. Depends on a compiler of course
-
Now now, I think that person is a great candidate for Yandere Simulator development.
-
@theabbie That depends on the language, and if the loop only goes once or twice or how many times the compiler/interpreter need to see before unwinding the loop.
Related Rants
-
Root5A sidebar. Literally just a sidebar. And yes, this was in Hell. Its code was spread across at least 40 files,...
-
Python3Adding a feature to 18 000 undocumented lines of code, written in PL/SQL. Oh, did I mention it was just a sing...
-
Voxera12On my former job we once bought a competing company that was failing. Not for the code but for their custome...
18000 duplicate lines that were manually copy pasted by the previous programmer.
I replaced them with a for loop.
I don’t think it was that hard…
rant
wk266