ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nim
For a Nim service handling only a few requests per second, the goal is to reduce steady-state memory and tail latency by selecting the ARC garbage collector instead of the legacy mark-and-sweep default. ARC reclaims objects deterministically at the point of last reference, avoiding stop-the-world pauses and potentially lowering resident memory for infrequent
The goal is to safely manage memory for a seq of objects that each define a =destroy destructor and may form reference cycles through their fields. When using the default ORC garbage collector ( --gc:orc ), cycles containing seq or ref are not reclaimed automatically unless the type is marked with the acyclic pragma or the cycle collector is invoked manually
Determine whether a library compiled with Nim's ARC memory management ( --gc:arc ) can be safely linked into an executable built with ORC ( --gc:orc ) without invoking undefined behavior. The Nim compiler permits pluggable memory‑management strategies, but mixing them across translation units is cautioned to cause runtime crashes or memory‑safety violations.
The goal is to make Nim GTK applications automatically convey accessible names and roles to assistive technologies such as Orca, reducing the burden on developers to invoke GTK’s Accessible API for every widget. However, the GTK Accessible API differs significantly between GTK 3 and GTK 4, the current Nim bindings expose only the raw widget interface, and th
Our Nim project recently moved to a toolchain whose Nimble version supports the nimble lock command and honors nimble.lock during nimble install . The repository is a library published to the Nimble package list, not a deployable application, and we need to decide whether the lock file belongs in version control. The tension we see: committing nimble.lock pi
Goal Determine if Nim’s experimental ARC garbage collector mitigates latency spikes that appear only under concurrent async requests. Constraints In Nim 2.x the default Boehm GC pauses the entire runtime during collection, which can cause noticeable delays when a burst of async or thread‑based requests triggers frequent collections. The asyncdispatch event l
Nim's garbage collector backend choice influences pause behavior during concurrent request handling, though pause-bound guarantees are not formally specified across versions. The --gc:refc flag shifts reclamation to reference counting while retaining a periodic cycle collector whose latency depends on heap size, allocation rate, and thread contention. Defaul
Nim's sequtils.chunks procedure provides a documented way to bound an in-memory sequence into fixed-size sub-sequences, which can act as a simple pagination layer when the dataset fits in RAM. For sequences that approach available heap, however, the practical boundaries of this approach remain unclear. Because each chunk produced by chunks is a new sequence,
After a failed Nim compiler upgrade, restoring a previous toolchain version requires choosing between two documented recovery paths, each with distinct risk profiles for existing project integrity. One documented path restores a previous compiler binary from the official archive, leaving installed packages intact, but may mismatch standard library modules wi