Swastik Baranwal
Swastik Baranwal
Heads up. I have implemented this feature in this commit https://github.com/Delta456/box-cli-maker/pull/22/commits/d7a6d036685c0736876fb03222984296dc87dde7 you can read how the future API would be.
Fixed this on my own! Bless xstrings library.
`else` is better for semantics. `default` is more for `switch`.
If we really want `case _` then the behavior of `_` should be like Go's. If it cannot be like that then `else` is better suited.
See [this](https://stackoverflow.com/questions/24357028/meaning-of-underscore-blank-identifier-in-go)
I am refering that `_` cannot be used anywhere in the program. If it does then it will raise an error. I know that so I think we should go...
> It seems like the discussion here is more and more circling about a different issue. Instead of discussing `case _` vs. `else`, it is more about the semantics of...
`for`/`while` only have else case when it exists the loop. As they have it. How about allowing `else` in both places i.e. : ```python match t: case P1(): case P2():...
@gvanrossum lol! Its an honor!
@Tobias-Kohn I know why you disagree but we need an `else` clause on the `case` level too. But imagine if we will have a `try` and `expect` then it leaves...