Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm sure you're already aware of this example since it's the canonical one, but to me personally the point is very clear: I use regular expressions all the time and always have to write that little bit of boilerplate, which the walrus operator now lets me get rid of.

Avoiding tedious boilerplate by adding nice features like the walrus operator is precisely what lets us avoid "death through a thousand little cuts to its ergonomics", in my view.

Sure, maybe writing

  m = re.match("^foo", s)
  if m != None:
    ...
isn't so bad, but in that case maybe writing

  i = 0 
  while i < len(stuff):
    element = stuff[i]
    ...
    i += 1
wouldn't be so bad, and we could get rid of Python's iterator protocol?


I think regex matches might be literally the only use case for := that I come across with any kind of nontrivial frequency, and it's only a minor nuisance at that. Certainly nothing to warrant an entirely new yet different syntax for something we already have.

The iterator protocol is way more general than what you have; it's not remotely comparable.


Regex is just a prominent example of a certain pattern. Depending on work and style, one often has functions which return something, on which in case of a non-empty result you want to do something more. Walrus can shrink the code in data-intensive code quite well from my experience.


I've come to like using:

    if foo := data.get("foo"):
        handle_foo(foo)


That’s exactly the same as this, though.

    foo = data.get("foo")
    if foo:
        handle_foo(foo)
The only place I have found the walrus operator useful is in similar `while` loops, where the equivalent code would be:

    while True:
        foo = data.get("foo")
        if not foo: break
        handle_foo(foo)


The loop can be written using This One Weird Trick that Walruses Hate:

  for foo in iter(partial(data.get, "foo"), None):
      handle_foo(foo)
So I would only use the walrus operator for the first example (the if statement), which even though it is exactly the same as doing it in two steps just feels nicer as a single step.


No it's not the same. The visibility of variable "foo" is extended beyond it's usefullness if you use `if`.


No, the visibility of `foo` is the same in both examples. Python’s `if` statements do not introduce a new scope.


It should have been “if … as y” and reused existing syntax. I’ve never seen anyone use the extended variant (multiple assignment) that walrus allows. The extra colons with this and typing makes it look like a standard punctuation-heavy language we sought to avoid in the first place.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: