I think we will have to see how it ends up used in practice. My main concern is how it might impact readability. It's not something that should be sacrificed for brevity of the code.,(reply>), @thomaskolar90 It saves you some lines which is totally useless. The main problem with compact code is that you need more brain power to read it. When you have 3 lines of code where every line do one thing you can read it easily, when you encounter a line with the walrus operator you have to evaluate that line in your head. It is a calculation, an assignment, and a condition check in one.,(reply>), @crazywayne yeah, I agree with the concern about feature creep, but I think this one is worth it. We add a bit of complexity of course, but I feel like the complexity we lose by not having extra control structures/multiple comprehensions is well worth it. In these cases I've always felt something I rarely feel when programming in Python, and that was that I was having to work around limitations of the language. There may now be two obvious ways to do some things, but there was never an obvious way to do this, at least if you've been spoiled by Python sufficiently to expect better.,(reply>), ​@thomaskolar90 you should love coding in obfuscated c, very short, and stylish<br>completely unreadable though,(reply>), @thomaskolar90<br><br>its less visual noise but for people who do not have much experience with python specifically it may be hard for them to easily understand how the operator works on the fly.<br><br>There is also the danger in the fact that more and more operators may get added which may cause the language to become overtly complicated if each addition is not vetted throughly.,(reply>), I think it's more readable tho tbh. Less visual noise is great.