Le 04/04/2012 02:41, Irakli Gozalishvili a écrit :
On Tuesday, 2012-04-03 at 14:07 , David Bruant wrote:
Le 03/04/2012 22:00, Irakli Gozalishvili a écrit :
Here is more or less what I have in mind:
https://gist.github.com/2295048
// class
var Point = {
(x, y) {
this.getX = { () { return x;
Other than the JQuery style misuse of this, what are the
use cases? If you want to bind this, why wouldn't a method
invocation on an objet be involved?
The ES array loops accept an optional this parameter to
be used for the loop callback.
It is up to the caller of the forEach to provide both
foo(a, b, ...rest)
vs
foo(a, b, rest...)
Which is clearer?
The former suggests a special construct that may have a name,
the latter suggests a variable of a special kind. But there isn't
anything special about the variable (a or b could be Arrays, too),
so I find the suffix form
Btw, why three dots? I always find myself writing two dots..
Presumably because three dots make an ellipsis, which has roughly
the meaning we're aiming for here.
True, and I admit to omitting that third dot in natural language
as well. But in the context of JS, if I think of ... as the
Claus Reinke wrote:
And I was surprised that both pro and cons camps continued the
discussion of recursive self and dynamic this naming as if no
workaround was available.
I don't think anyone is really pushing hard for a dynamic-|this| form
(say, -) right now. Perhaps some want it but the
From http://www.scala-lang.org/node/4723 (hat tip *Corey
Farwell*@*frewsxcv* https://twitter.com/#%21/frewsxcv
*
):
|= ⇒ // implemented
- ← // implemented
- → // implemented
== ⩵
≫
≪
⋙
= ≥
= ≤
:: ∷|
Corey suggested editors could do the input conversion when
6 matches
Mail list logo
