does it seem reasonable though that if properties get initializers in the
class body that they could be considered in scope to everything else
defined in the class body?
On Jul 27, 2015 6:52 PM, Brendan Eich bren...@mozilla.org wrote:
Michael McGlothlin wrote:
I'd rather that prop just match
Matthew Robb wrote:
does it seem reasonable though that if properties get initializers in
the class body that they could be considered in scope to everything
else defined in the class body?
That's a big if, but with the right *declarative*, binding-like
syntax, that's plausibly valid
Hi.
In CoffeeScript (and a few other languages including Ruby I believe), there is
a syntax shortcut for simplifying accessing properties on the current context
(this variable), which is something you have to do often.
This looks something like `@prop`, which is synonymous with `this.prop`.
Ah yes, silly me.
What about %prop or $prop? When it’s something you have to do a lot, repeatedly
typing `this.` can be a pain. There’s definitely a case for it as many other
languages use it.
--
Nathaniel Higgins
Sent with Airmail
On 27 July 2015 at 14:46:33, Andrea Giammarchi
apparently the @ has been booked already for decorators
https://medium.com/google-developers/exploring-es7-decorators-76ecb65fb841
I also personally think we don't really need yet another magic shortcut
that but that's just my opinion.
Best Regards
On Mon, Jul 27, 2015 at 2:23 PM, Nathaniel
I'd rather that prop just match the object the method is actually attached to,
regardless of the context of 'this', before continuing searching the tree.
Familiar as its done that way in many languages, short, and independent of
'this' context.
A context operator might be a good idea though.
the real bummer to me is that `with` statement has been deprecated and
killed without a replacement but AFAIK the dot-stache operator should
come to save us from typing:
```js
this.{
doStuff();
doMore();
prop = Math.random();
console.log(prop);
}
```
although I cannot even find the
Michael McGlothlin wrote:
I'd rather that prop just match the object the method is actually
attached to, regardless of the context of 'this', before continuing
searching the tree. Familiar as its done that way in many languages,
You mean static (applied to types, including fields in objects)
8 matches
Mail list logo
