Re:"I couldn't really learn Erlang, 'cos it didn't exist, so...
by klibertp on Thursday January 24, 2013 @10:26AM
(#5109971)
In short, in your opinion, Python has no "complete" closures because you cannot bind a new value to the name from enclosing lexical scope from within a nested scope. I disagree.
[ Parent
| on HN ]
Re:"I couldn't really learn Erlang, 'cos it didn't exist, so...
by effn on Thursday January 24, 2013 @11:26AM
(#5110324)
This is not possible in Haskell either. You never hear people claiming Haskell doesn't support closures.
Re:"I couldn't really learn Erlang, 'cos it didn't exist, so...
by klibertp on Thursday January 24, 2013 @11:42AM
(#5110443)
Which is why I disagree with claims that Python doesn't support them either. It does, of course; we could argue if Python supports "complete" closures, but we won't, because we know better than to use meaningless terms in discussion, right?
Re:"I couldn't really learn Erlang, 'cos it didn't exist, so...
by koide on Thursday January 24, 2013 @12:12PM
(#5110667)
In any case it's not been the case in a while, so I stand corrected.
Although being able to write on the closed over variable is a neat feature to have, I would argue that feature does make a difference. Whether you call that complete or read-write or however you want to.