ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Nim's standard library httpclient reuses TCP connections via keep-alive through an internal connection pool. In applications that issue many concurrent requests with asyncdispatch , the pool can saturate when the number of in-flight requests exceeds the hard-coded idle-connection limit per host. Because the stdlib does not expose a public API to tune the poo
I am designing a Nim service where async request handlers (std/asyncdispatch) occasionally need to call a legacy blocking library. The documented escape hatch is std/threadpool's spawn, which returns a FlowVar[T], but a FlowVar cannot be awaited natively inside an async procedure. The options appear to be polling isReady in a loop with sleepAsync, blocking o
A small Nim application using the async module needs to be moved to Nim 1.0 without changing runtime behavior. The documented compatibility boundary is the introduction of asyncdispatch as the default scheduler in Nim 1.0, which replaces the older async module's single-threaded event loop with a thread-pool based implementation. The change is recorded as a b
nim