I don't know...to me this looks downright ugly and an awkward special case.
It feels like it combines reading difficulty of inline assignment with the
awkwardness of a magic word and the ugliness of using ?. Basically, every
con of the other proposals combined...
--
Ryan (ライアン)
Yoko Shimomura,
IIRC in CPython 3.6 and PyPy dicts are ordered based on insertion anyway;
although it's an implementation-specific detail, realistically it removes
some of the use cases for ordered dictionary literals.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone
So, I'm hardly an expert when it comes to things like this, but there are
two things about this that don't seem right to me. (Also, I'd love to
respond inline, but that's kind of difficult from a mobile phone.)
The first is how set/get_execution_context_item take strings. Inevitably,
people are
This is literally PyPy. There's little reason for something like this to
end up in official CPython, at least for now.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jul 1, 2017 at 5:53 PM, > wrote:
On 2017-07-01 07:34 PM, Victor
I feel like this would literally break the world for almost no real
benefit...
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jun 29, 2017 at 6:33 PM, > wrote:
Step 1. get rid of + for strings, lists, etc. (string/list concatenation
IIRC I'm pretty sure the OP just didn't know about the existence of tuple
unpacking and the ability to use that to return multiple values.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jun 25, 2017 at 6:09 PM, > wrote:
joannah
For some background on the removal of __instancecheck__, check the linked
issues here:
https://github.com/python/typing/issues/135
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jun 25, 2017 at 8:11 AM, > wrote:
On Sat, Jun 24,
