#Can I optimize this code or is it already optimized to the maximum?
7 messages · Page 1 of 1 (latest)
there's no "optimized to the maximum"
you can keep optimizing pretty much anything, but you get diminishing returns
it's just about how optimal is optimal enough
changing == to === would improve correctnes quite a bit and optimize it marginally
(== is shit, don't use == unless you absolutely know its exact behavior)
you're using any a lot, you shouldn't do that
this code needs correctness improvements before optimization
also this is quite complex and involved, i doubt many people are gonna be willing to go through to understand your entire code to provide detailed feedback about optimization