* Listed the downsides of the current proposal.
* Listed why '<cond> then <expr1> else <expr2>' is starting to
be preferred over '<cond> and <expr1> or <expr2>'.
* After BDFL comments, I withdrew my proposed c??a||b syntax
and deleted the rejected c?a!b syntax. The remaining
punctuation based contender is c?a:b.
* After BDFL rejection of non-short-circuiting options,
advocacy dropped sharply. Removed it from the list of
contenders.
The leading options on the table are:
* (if <cond>: <expr1> else: <expr2>)
* <cond> then <expr1> else <expr2>
* <cond> ? <expr1> : <expr2>
* no change
* Out of order evaluation is out of favor.
* So are ideas that do not provide for short-circuiting.
* (if <condition>: <expression1> else: <condition2>) is in vogue.
* <condition> ?? <expression1> || <expression2> is a new contender.
* cond(<condition>, <expression1>, <condition2>) is viable if implemented
as a keyword and has short-circuit behavior.
* Added a summary of a few ideas from the last couple hundred posts
from comp.lang.python.
Guido van Rossum
Raymond Hettinger
David Goodger
Skip Montanaro