Adam Fraser
Adam Fraser
Yes, reopening to track it. Unfortunately this combinator is not resource safe with the current encoding of specs because we need to evaluate all the specs to determine whether there...
@jypma You can already filter for a certain test with `testOnly zio.ZIOSpec -- -t "fiber interruption"`.
Do you control this code so you can not call that? In ZIO 2.0 we added an `exit` operator on `ZIOApp` for this.
That makes sense to me. The main downside I see is that it makes serialization logic more complex.
This is something we have talked about, primarily around debugging and being able to "step through" the workflows of a fiber similar to how you would with imperative code. I...
Do you know how we can tell whether we are running on it? Is there a system property that reflects that?
Do they work on ZIO 1.0? Do we have another issue that we need to figure out first?
@tewecske I think we are close enough to release of ZIO 2.0 that we should be focusing new development there.
@domdorn Thanks for jumping in on this!