On 07/29/2019 06:35 PM, Steven D'Aprano wrote:
3. syntax that solves a problem, but may mislead people to think it solves a different problem until they learn better;
3.1 syntax that solves a problem, but is misleading to many who are still confused after they "have learnt better"
I feel your pain: I don't understand async code when I see it either.
Neither do I, but I have no need to. I do have a need to use for...else, and every time I do I have to think through the "this is a search loop" to get the right semantics (sorry for bringing that up again, but it's a great example). If this "with...except" leads to more robust code then I think many would like to use it, but not if it's confusing as that would lead to less robust code. -- ~Ethan~