Ah, ok, I suppose that could easily lead to typo-bugs. Ok, then I agree
that "a:=f()" returning a is better
On Fri, Apr 6, 2018 at 10:53 AM, Eric Fahlgren <ericfahlg...@gmail.com>
wrote:
> On Fri, Apr 6, 2018 at 7:47 AM, Peter O'Connor <peter.ed.ocon...@gmail.com
> > wrote:
>
>> 3) The idea that an assignment operation "a = f()" returns a value (a) is
>> already consistent with the "chained assignment" syntax of "b=a=f()" (which
>> can be thought of as "b=(a=f())"). I don't know why we feel the need for
>> new constructs like "(a:=f())" or "(f() as a)" when we could just think of
>> assignments as returning values (unless that breaks something that I'm not
>> aware of)
>>
>
> Consider
>
> >>> if x = 1:
> >>> print("What did I just do?")
>
>
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
