Ross A. Baker

> if the libs diverge My understanding of the compatibility guarantee is that this should not happen: all code compiled with TLS should link with the LBS runtime, and vice...

I also thought that scala-library was bidirectionally compatible across patch releases since 2.10. I would rewrite the POM from TLS-2.12.3 to LBS-2.12.3, so we'd be fine, but I'm also surprised...

http4s is publishing with the latest TLS version, and does not use `ValueOf`. We adopted TLS early to help test it, with the understanding that it was transparent to downstream...

@nigredo-tori mentioned http4s-0.17.0-M3 on Gitter, which depends on TLS 2.12.1. http4s-0.17.0-RC1 depends on TLS' 2.12.3-bin-typelevel-4. To achieve transparency, I think we need to be producing POMs that declare LBS 2.12.3,...

And this problem mixing organizations applies through transitive dependencies? I would think this mixing would be quite common: * foolib builds against LBS 2.12.x * barlib builds against TLS 2.12.y...

I just wanted `==>` and `:|` whilst trying to eliminate some `unsafeRunSync()`.

I think the problem is we're releasing the permit (acquired line 299) after returning items to the pool (line 307), not when the connection is dropped from the pool. https://github.com/typelevel/keypool/blob/41c4f5177f8b1e904c19d48b95cfd26fd9d9bbea/core/src/main/scala/org/typelevel/keypool/KeyPool.scala#L298-L312...

It's more fiddly than that: if we don't release when we return the connection to the idle state, then if the pool is full of idle connections, no connection can...

So the cats-effect-std dependency landed in core, but `IOLocal` would require the full cats-effect. Doing that would pull cats-effect (and `IO`) into all the downstream projects that limited themselves to...

I would have thought so, until cats-mtl's future stability was questioned on [this pull request](https://github.com/typelevel/cats-effect/pull/3429). The uncertainty around that statement is blocking a cats-effect PR, a clear path forward on...