Georgi Krastev
Georgi Krastev
Ah yeah, you're right - the semaphore protects the parallelism, once a fiber is completed, the permit will be released. And it wouldn't be put into the queue before it...
> And it wouldn't be put into the queue before it started. I meant to say that there's no point to set parallelism > buffer size. If you can't start...
> I don't think Scala 3 has anything that facilitates this, but please correct me if I'm wrong. In Scala 3 you could write this: ```scala def runSession[S](p: S)(using s:...
That looks like the correct behaviour to me. Consider this relation: ```scala scala> implicitly[(op.Cap forSome { val op: Op })
Type projections are not implemented as existentials. Anyway let me show an example that will hopefully convince you why `O
We all know by now that general type projection is unsound. However I don't see any bad bounds in the animal example. The problem would arise exactly from having two...
I think it's possible to offer a scalafix rewrite that could even be applied by scala-steward. This could be done together with deprecating the old methods.
@disordered we can't do zipping in `flatMap` because the inner `Gen` can depend on the outer one. We could reimplement `Gen.zipWith`, however check similar methods like `concat`, that would again...
We could use this at $work. How does it look?
Another use case is to be able to set a deadline on the `CallOptions` based on the method descriptor. Currently that's not possible because the client call is already created...