why aren't normal assignments expressions," like in Java or c?<br>and how is it error prone? (<a href=""https://www.youtube.com/watch?v=KN2TTiGpDvM&amp;t=4m43s"">4:43</a>)<br>I have never made an error regarding assignments",(reply>), ​@Maxi In that case, this joins the ranks of the few reasonable discussions on YouTube,(reply>), @Logan Kaser don't worry, I didn't see your comment as a counter-argument, I simply explained why I don't think the walrus operator is necessary.,(reply>), @Maxi I've used it I'm not advocating against that, and I don't make this mistake personally. However, it is one of the few syntax errors that is commonly mentioned in textbooks as an easy mistake which is why people bring it up. Unlike the other common typo people complain about (&amp; vs &amp;&amp;) the compiler has no good heuristics it can use to warn the user.<br><br>You seem to have assumed I'm arguing against you, In reality, I just answered your question and explained why the video dismissed the complaint that it is error prone (since the different symbol means that the C argument does not apply to python),(reply>), @Logan Kaser I have literally <i>never</i> done that... Also, of course that can happen; If you make a mistake, your code won't work as expected or at all. That's the same with anything!<br><br>I use the normal assignment in java and c and think it's definitely more intuitive and especially: <b>consistent</b> than making up a whole nother operator for it.<br>I'm not stupid, I don't need something more fool proof...<br><br>Also, the same can be said for == and ===, it <i>could</i> go unnoticed, but they didn't invent a different symbol just to accommodate for stinky people,(reply>), I think it is referring to the `if (a = b)` vs i`if (a == b)` typo that can more easily go undetected (with python's duck typing probably <b>very</b> easily).<br>However, the := is has a ":" so it should not suffer from this issue and the criticism is not very valid.