node package manager
It’s your turn. Help us improve JavaScript. Take the 2017 JavaScript Ecosystem Survey »



ABANDONEDTurns out that if you just hammer on v8's bind() enough times it gives basically the same performance as manually inlining anyway :P So there is no point to using this library (ie the concept is flawed)

An optimizing implementation of partial function evaluation for JavaScript in JavaScript. Speed ups for free!


var specialize = require("specialize")
//Create a test function 
function testFunc(a, pred) {
  if(pred(a)) {
    return a + 10
  return a - 10
var specialized = specialize(testFunc, undefined, function(x) { return x > 0 })
//Prints out 11 
//Prints out -11 

require("specialize")(func, arg1, arg2, ...)

Optimizes func by binding static values from arguments to the scope of function.

  • func is the function to bind
  • arg1, arg2, ... are the arguments for the function to specialize. Pass in undefined to skip specialization.

Returns A specialized version of func


Because objects have properties that can change over time this code doesn't support inlining objects. If you do pass an object it gets bound dynamically, just like calling bind() and so there isn't much benefit to this library. It is also possible to inline functions which use variables from their outside scope. An exception is made for variables in the global namespace even though this is not technically correct (since they could be rebound in a shadowing closure). This is a conscientious choice, and if you want to overload globals then you should just use bind().

What it can do is inline constant values and some closures for well encapsulated functions, giving a substantial speed up with little loss of flexibility.

Experimental results

After experimenting a bit, I discovered that at least in v8 there is really no point to doing all this since the native implementation of bind already does partial evaulation for you. So there is really no need for this library :P.


(c) 2013 Mikola Lysenko. MIT License