This abuses errors in the fixed-point math, to have the first "error" line up exactly where we want, on that final leap second.A round-down multiplier is used, with a pre-increment, as that is the type of adjustment that yields an eventual long-minute and long-hour.
I would say that 90% of devels would look at this and have no clue what is going on or why.
This is something to be done in the compiler, but not in the code unless there's some actual slow down in the code that is visible via benchmarking.
5 Comments
bort@sopuli.xyz · 15 pts · 6d
i love it
pHr34kY@lemmy.world · 8 pts · 6d
If everyone coded like this, we wouldn't have so many data centres spewing soot into the sky.
Test_Tickles@lemmy.world · 13 pts · 6d
I would say that 90% of devels would look at this and have no clue what is going on or why.
This is something to be done in the compiler, but not in the code unless there's some actual slow down in the code that is visible via benchmarking.
cafuneandchill@lemmy.world · 2 pts · 6d
This is utterly incomprehensible tbh, but I guess I'll believe it
Deebster@infosec.pub · 5 pts · 5d
I understand it with the given explanation, but I would be utterly mystified if I came across this code in the wild.