Sorry for the clickbait. It’s so omnipresent these days, I had to try it. 90% of my daily Medium digest and 90% of my Pocket recommendations are like this. Note to self: write some kind of clickbait filtering software. Obtaining a huge training set should not be an issue. (We could even crowdsource these! How fun!)
In some cases, Crankshaft doesn’t optimize a function. It simply gets to a function and bails out instead of trying to optimize it. Whenever this happens, it invokes a bailout reason.
Documentation on these bailout reasons are very scarce, so Wednesday I decided to list them all and try to reproduce each of them, documenting why it occurs, giving advice on how to avoid the bailout, and give real-life examples of where it can be spotted.
As of the writing of this post, I was only able to partially document 8 of them. I have more material but need more research/more time.
If you’d like to see what I got and to contribute your awesome V8 knowledge, please see V8 bailout reasons on GitHub.
But I didn’t make you read all this for nothing. In the title of this post I made a promise I intend to fulfill, so here is…
Don’t use more than
Stick to 511 parameters (or less).
- 511 is a good-looking number. In unicode, it looks really really good: ǿ
- A function with 511 parameters always looks better than a function with 512 parameters. (I have discovered a truly remarkable proof which this margin is too small to contain.)
Note: I originally wrote this article with 65535 instead of 512. I did not pay enough attention while reading V8 source code. It was 65535 bits, i.e. 512 bytes, or 512 parameters. Not 65535 parameters. Review the diff.