Brendan Eich (2013-07-26T17:35:15.000Z)
domenic at domenicdenicola.com (2013-07-31T15:00:14.008Z)
Arguing with myself... Brendan Eich wrote: > Optional parameter list is an easier sell since `=>` is very unlikely to > start a statement, while `=>` may well end one "may well" is too strong. My example in reply to Oliver was ```js var empty = => callLater(empty, "sorry"); ``` But it's hard to think of anything else that might end an intended statement with `=>`. Anyway, thanks for bringing this up. Sometimes TC39 needs to reach consensus in stages, e.g., maximin classes, only then to realize what most people could see: we need less minimal maximin (e.g., class "statics"). Could happen with arrows, but I wanted to provide some more detailed guidance -- and a cautionary tale re: CoffeeScript.
domenic at domenicdenicola.com (2013-07-31T14:59:53.087Z)
Arguing with myself... Brendan Eich wrote: > Optional parameter list is an easier sell since => is very unlikely to > start a statement, while => may well end one "may well" is too strong. My example in reply to Oliver was ```js var empty = => callLater(empty, "sorry"); ``` But it's hard to think of anything else that might end an intended statement with `=>`. Anyway, thanks for bringing this up. Sometimes TC39 needs to reach consensus in stages, e.g., maximin classes, only then to realize what most people could see: we need less minimal maximin (e.g., class "statics"). Could happen with arrows, but I wanted to provide some more detailed guidance -- and a cautionary tale re: CoffeeScript.