Domenic Denicola wrote:
Slide 31 ends with a question: // what about `module.exports= aFunction`?
Cc'ing dherman.
Yeah, since there will be lots of Node-ers there, and this is their #1 feature,
I thought it was important to point out there's no solution for that yet. In
general my impression is that modules are undergoing some rethinking and
revision, especially about syntax. It's tricky, since even if I cut those
slides, I want to e.g. import iterator, but am not sure what syntax to use :-/.
import iterator from "@iter";
is ok if you then use obj[iterator]. It may be we want to support both
this and
import @iterator from "@iter";
which would support obj.@iterator = ... subsequently
Slide 33 has a recursive call not in tail position:
Damn, OK, I thought my example met the definition at
http://wiki.ecmascript.org/doku.php?id=proposals:proper_tail_calls (in particular "the only
thing the caller can do when the call terminates" is "return the value of the call to its
own caller"). It sounds like I don't quite understand tail recursion still, so thanks for the
link---I'll brush up.
There's a + operation in flight in the caller.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
