Re:Where are we in the Python 3 transition?
by alextgordon on Friday January 01, 2016 @05:21PM
(#10823766)
Other languages seem to get it right. Even C++!
[ Parent
| on HN ]
Re:Where are we in the Python 3 transition?
by millstone on Friday January 01, 2016 @05:59PM
(#10823917)
C++ its own insane behavior, where default arguments are determined at the call site instead of at runtime. This means your function can get another function's default arguments.
#include <iostream>
struct Base {
virtual void foo(const char *name = "base") {
std::cout << "Base impl with " << name << " param\n";
}
};
struct Derived : public Base {
virtual void foo(const char *name = "derived") override {
std::cout << "Derived impl with " << name << " param\n";
};
};
int main(void) {
Base *b = new Derived();
b->foo();
}
prints "Derived impl with base param"Fortunately Python avoided that bit of silliness.
Re:Where are we in the Python 3 transition?
by denim_chicken on Friday January 01, 2016 @08:01PM
(#10824413)
This behavior is pretty reasonable to me.
Re:Where are we in the Python 3 transition?
by eiopa on Friday January 01, 2016 @05:41PM
(#10823847)
ES6 got this right too.
This design decision makes me die a little every time I have to do:
def foo(x=None):
if not x:
x = []
...
Re:Where are we in the Python 3 transition?
by dajonker on Friday January 01, 2016 @05:53PM
(#10823900)
That will get you into trouble as well, please use:
if x is None:
x = []
... etc.
Re:Where are we in the Python 3 transition?
by switch007 on Friday January 01, 2016 @06:12PM
(#10823992)
Or even "prettier":
x = [] if x is None else x
Re:Where are we in the Python 3 transition?
by knite on Friday January 01, 2016 @06:51PM
(#10824182)
I'm partial to:
x = x or []
Re:Where are we in the Python 3 transition?
by acveilleux on Friday January 01, 2016 @08:01PM
(#10824409)
Only works when x is truthy for all legal x values, excluding x=0.
Re:Where are we in the Python 3 transition?
by nbadg on Friday January 01, 2016 @06:09PM
(#10823976)
I'm not familiar enough with the innards of other languages to make any definitive comments on it, but I will say that the challenge is in combining a high-level language with late-binding closures with memoization. I'm not aware of a strategy for that which is always intuitive for every program you write; I think it's just a language design combination that has a very high probability of developing "gotchas" no matter what you do.
Also, on a related note, I really love late binding and memoization, so I'm definitely biased on the side of "I understand why the language designers made this decision, and though the ramifications bother me a little bit, I much prefer this way".
On a third note (because hey, why not), with type hints being a thing now, maybe it would be worth considering a default eval hint. It could default to current behavior, and therefore retain backwards compatibility, but you could add syntax to declare defaults as new variables. That might be a smart compromise.
Small tip: you can shorten your snippet by completely removing main's parameters and the return 0 and still have a valid c++ program.
Re:Where are we in the Python 3 transition?
by alextgordon on Friday January 01, 2016 @06:10PM
(#10823979)
I did pause to think about this, but sod's law dictates that if you remove the parameters to main, you will have to add them back in again. :)