Matthias Berndt
Matthias Berndt
@vigoo It's passing CI now, so I think it's ready to merge
I have to say that I find the idea of merely typing it as `Cause[Nothing]` somewhat unfortunate. Typed errors are a staple of ZIO and merely extending the set of...
I'd like to propose a type-safe alternative in #566.
If the aggregation behaviour is implemented, there should be a configuration parameter to limit the maximum size to avoid DoS.
Hey @soronpo, [I'm sorry, I'm afraid I can't do that](https://youtu.be/7qnd-hdmgfk). Please consider the following enum: ``` enum Foo: case Bar case Baz(f: Int => Int) ``` I'm going to contend...
Hi @JD557, > Do we need a `CanEqual[Foo, Foo]` for the pattern match? Wouldn't a `CanEqual[Foo, Foo.Bar.type]` suffice? > > Now, from what I can tell based on some quick...
> Let me clarify. If you want function arguments that should not be part of the pattern match, then these should come as a second argument block of the case,...
I've pushed a new revision that is based on a minor change to `enum` pattern matching and a magic `CanEqual` instance. @soronpo please let me know what you think
Hi Oron, I have considered the committee's proposal and would like to present my conclusions. 1. When applied to the motivating `Nat` example in the SIP, the committee's proposal would...
Hey @soronpo Yes, you're right, that code does not compile under the rules I've proposed: `Any` cannot be equality-compared to an `Int` or a `String`. I think that's fine. The...