nimony-ts — idiomatic TypeScript backend

An idiomatic TypeScript backend for nimony: Nim types become real TypeScript types, not byte offsets.

Status: early scaffold · private repo. The architecture is being designed; no working codegen has landed yet. Access via Discord timbuktu_guy.

Different from nimony-web

nimony-web already takes Nim to the web, but over a linear-memory model — one ArrayBuffer, pointers are integers, objects are byte offsets (HEAP32[p>>2]). Fast and faithful, but the output is asm.js-style, not something a TypeScript developer would read or type-check. nimony-ts is the opposite trade-off: idiomatic, readable, fully-typed TS.

	nimony-web (nim-js)	nimony-ts
memory	one ArrayBuffer, offsets	real JS objects, engine GC
object	bytes at a byte offset	interface / class
seq[T]	header+data in the buffer	T[]
string	linear bytes	string
output	fast, faithful, asm-style	readable, typed, idiomatic

They’re separate projects on purpose — the one asset that unifies nimony-web (the jslayout byte-layout engine) is exactly what an idiomatic backend throws away.

Planned architecture

The idiomatic mapping consumes nimony’s sem’d, pre-hexer NIF — the .s.nif artifact nimony already writes unconditionally — which is dramatically more idiomatic than the post-hexer .c.nif that nimony-web consumes:

construct	.s.nif (consumed here)	.c.nif (nimony-web)
echo "x"	(cmd write stdout "x") — literal intact	LongString refcount struct + SSO
object	nominal, named fields	bytes at a byte offset
seq[T]	generic (at seq T)	header+data+cap struct
try/raise	structured TryS/RaiseS	error-code returns + goto

The Nim-semantic lowering is shared with nimony-py via nimony-hl; nimony-ts is the thin emitter that renders the High-Level IR into TypeScript.