On 2019-04-09 12:54, Nikita Popov wrote:
Inspired by Bob's recent RFC for concat precedence, I'd like to propose
a
deprecation and removal of the left-associative behavior of ternaries.
Instead, explicit parentheses should be used: ...
What about nesting in the middle part: 1 ? 2 ? 3 : 4 : 5
T
> Le 9 avr. 2019 à 12:47, Nikita Popov a écrit :
>
> On Thu, Apr 4, 2019 at 1:16 AM Andrea Faulds wrote:
>
>> Nikita Popov wrote:
>>> I'm always a fan of making things stricter, but think that in this
>>> particular case there are some additional considerations we should keep
>> in
>>> mind.
> Le 13 avr. 2019 à 11:09, Stijn Peeters a écrit :
>
> Is anyone aware of other arguments for not allowing normal arguments after
> unpackable arguments in function calls?
I've grabbed into the archives of internals. Apart from technical issues:
The main argument against that affordance was
On 13 April 2019 10:09:20 BST, Stijn Peeters wrote:
>Is anyone aware of other arguments for not allowing normal arguments
>after
>unpackable arguments in function calls?
CHU Zhaowei pointed to this git commit which suggests it's an implementation
issue rather than a design decision:
https://git
"Dan Ackroyd" schreef op 6 april 2019 07:37:
> On Fri, 5 Apr 2019 at 09:03, Claude Pache wrote:
>
>> That begs the question: why is this invalid for function calls?
>
> At least in part, because if we ever wanted to add a standard
> _toArray() method, like we have __toString(), it would be qui
