Better stack traces

So we’ve just shipped new stack traces in RunKit, and I’d really like Ramda to have easier to read stack traces (even outside of our tools). Currently it contains lots of Object.f2s and such, and I did a few experiments with setting functions names.

Here you can see what Ramda looks like currently:

( https://runkit.com/tolmasky/ramda-current-traces )

And here is what they could look like:

( https://runkit.com/tolmasky/ramda-better-traces-22 )

Basically, the trick is to do something like this:

function functionNamed(aFunction, aName)
{
    Object.defineProperty(aFunction, "name", { value: aName });
    aFunction.displayName = aName;

    return aFunction;
}

[CrossEye]

I was hot on this some time back, using techniques from https://medium.com/@drboolean/debugging-functional-7deb4688a08c#.f0g8hif9c but I never got finished with it. I would love to see something like this in the library, as much for debugging consoles as for stack traces.

It’s a fair bit of work, but I think it would be worth it.

[CrossEye]

Feel free. I absolutely think it is worth doing.