Taine Zhao
@Tobias-Kohn Thanks, I now think `|` is quite okay. That is because the precedence is still correctly consistent to the use of `|` in an expression. Come back to Guido's...
@DimitrisJim > saying hackers/experts are open to new ideas implies that people not belonging in that group are not open to new ideas, which some people might take offence with...
Consider #100 ? Needs no `__match_args__`. A default implementation made for `object` will allow keyword patterns without doing any pre-settings. For the possible reason that you rejected this... > I...
Okay, but could you please show this?: > does not solve this issue being addressed here.
Clairfy: Despite of `__match_args__`, defining `__match__` later will also break the backward compatibility. This cannot get avoided because users can arbitrarily decide the first pos arg `x` for a pattern...
Some analyses: 1. why we want a default behavior? > ... aims at providing a basic, useful (but still safe) experience with pattern matching out of the box 2. actual...
Yes, implementing range patterns with dedicated syntax is a waste. We can implement this with current protocol.
If you can support parameterised patterns in some way, it won't be obfuscated at all.
https://github.com/jspahrsummers/adt/issues/18
FYI, the results of Python stdlib `cmath` is the same as the Julia's. ```python import cmath cmath.atanh(-3 + 0j) # (-0.34657359027997264+1.5707963267948966j) def asech(x): return cmath.acosh(1/x) asech(-3 + 0j) # -1.9106332362490186j...