> Hm. Maybe you meant to return the function to allow access to the local
> variable
> k through a closure? And not a fingerprint
> mixed shift(function)
> as I read it at first?
I don't know what you're saying, but I have already posted the semantics in
this thread. I *think* it should be prett
> I don't understand this question-- do you mean whatever value the
> handler function (in the example, function(k) { return k })
> returns? Then no, there's no augmentation or mutation here. The
> continuation is represented as an object with three methods:
Ah, I didn't know that.
>> It'd be cle
> What happens if you don't supply a function but another type, or none?
The simplest thing is to specify it as a runtime error if the argument to shift
is not callable. You're right that there's an overhead to constructing a new
function. But it gives you flexibility that's otherwise a pain for
Why does the specification state "Error instances have no special properties"?
The ES5 specification states:
| 15.11.5 Properties of Error Instances
| Error instances inherit properties from the Error prototype
| object and their [[Class]] internal property value is
| "Error". Error instances hav
4 matches
Mail list logo
