Vasil Vasilev

The integration point of this experiment is not with Cats Effect (I only imagine that we would need to call a couple of library methods in the `WorkerThread/WorkStealingThreadPool` constructor methods...

I'm not opposed to deprecating `readLine`.

I like the proposal.

Out of curiosity, does anyone know what would be a blocker to implementing `java.lang.Thread` on top of pthreads?

@djspiewak Maintainers have a way to force the discovery and update if necessary, through the GitHub website.

If I can weigh in on the issue, I would like for things to stay as they are. I don't think we've missed updating the docs right after I release...

Can you please test if this is happening in 3.3.8 or maybe some other version too? It would be nice to find out if this is a bug for some...

Reminds me of https://github.com/scala/bug/issues/9076.

First of all, thanks for raising this issue. Is this on the `3.2.9` release? We've actually made changes to these code paths which will be released in the `3.3` release....

This issue reminds me of this one https://github.com/typelevel/cats-effect/issues/1995.