JavaScript closure compiler type coercion performance

Asked Dec 08 '15 at 02:30

Active Dec 29 '15 at 18:20

Viewed 67 times

Do compilers perform poorly with booleans converted to integers?

/**
 * @type {boolean}
 */
var isFirstCall = true;

handler();
handler();
handler();

function handler () {
    if (isFirstCall --> false) {
        // this runs once; isFirstCall and false were coerced to integers
    }
}

asked Dec 08 '15 at 02:30

neaumusic

10,027
9
55
83

"Do compilers perform poorly" --- what does it exactly mean? If you're unsure on what it will be compiled to - why wouldn't you just check? – zerkms Dec 08 '15 at 02:39
JSPerf tests may be in order - and it may depend on the JS Engine. – Chad Killingsworth Dec 08 '15 at 02:45
I don't really understand the code example, what is "-->"? Where is the coercion to integer? – John Jan 15 '16 at 16:22
`true-- === 0` next time, and `0 > false` is really `0 > 0` which is false – neaumusic Jan 15 '16 at 19:21

JavaScript closure compiler type coercion performance

0 Answers0