Zohaib Sibte Hassan

Would be trying to reproduce your bug

just did it :D here it is https://github.com/madrobby/emile/pull/10

Feel free to send a PR.

I think what @amit-handda is mentioning is more specific for reactive solutions (In this case Kotlin coroutines which are non-blocking on threads). I think having this in place will unlock...

> The results you are referring to, where future-based and non-future based tasks are compared, what polling-strategy are they using, and what limits? So the reactive systems that I am...

Any updates on if this can be merged? This will really unblock a lot of use-cases.

If we can do that and release it a some sort of beta package. I can write some reactor benchmarks as well.

I think couple of issues being mixed here: - Some clients may misbehave and have these weird states, but that is a different problem to tackle. Frameworks like Netty, Undertow...

@kagkarlsson virtual thread are in EAP and even after rollout just like record classes it's gonna take years for people to move over. All of existing library and software stack...

I've been waiting for this for a while now. I threw the towel because it was choking Marmot from the ease of peer discoverability via DNS in environments like fly.io,...