arguments.callee breaks inside generated closures

[hen-x]

This may come as a shock to absolutely no-one, but the value of arguments.callee changes inside generated closures:
test = ->
callees = arguments.callee for i from 0 to 0
callees[0]

test() is test # false      

One possible solution is to cache the value of arguments in the outer function, and then reinstate it in the closure, rather than passing it with apply():
var test;
test = function() {
var _result, callees, i, self;
var _arguments = arguments;
callees = (function() {
arguments = _arguments;
_result = [];
for (i = 0; i <= 0; i++) {
_result.push(arguments.callee);
}
return _result;
}).apply(this);
return callees[0];
};
test() === test; // true!
I don't know if arguments is made mutable by the spec, but this hack works in v8.

[zmthy]

Woah, I didn't realise Coffeescript compiled that way. The most appropriate solution would be to pass it through as an argument, using call instead of apply.
value = (function(arguments) { ... }).call(this, arguments);

[hen-x]

@Tesco: Nice, and much cleaner! I'm amazed that having an argument a parameter named arguments actually overrides the default value.

[satyr]

SyntaxError in strict mode.

[zmthy]

Darn. Reverted, reopening.

[zmthy]

arguments gets the honour of pretty much being a keyword in strict mode. There's no way for us to fix this while taking that into consideration - just don't use the callee property, save the function to a variable instead (or implement the function keyword :D).

[satyr]

FYI: satyr/coco#4