7 Commits

Author	SHA1	Message	Date
Ivan FB	0e176bd5eb	fix(ffi): set up foreign-thread GC in entry procs; recycle/event cleanup ... - Call initializeLibrary() (setupForeignThreadGc) in the `.ffi.` request wrapper and in add/remove_event_listener so a foreign (Go) caller thread has an initialised Nim heap before any allocation ($reqTypeName / $eventName / registry ops). Without it such a thread segfaults in the allocator under GC pressure — the production unwrap SIGSEGV. - recycleContext resets the event registry/queue + stuck flag on park so a reused pool slot starts clean. - ffiDtor doc/cleanup for the async recycle ABI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-12 11:28:48 +02:00
Ivan FB	0170d7c469	update changelog and ffi.nimble for v0.1.5	2026-06-11 15:34:36 +02:00
Ivan FB	c2ea4f3f98	add changelog for 0.1.4	2026-06-11 15:26:27 +02:00
Gabriel Cruz	9b3cde7674	feat: move user event code to a dedicated event thread (#69)	2026-06-09 11:35:04 -03:00
Ivan FB	721f244312	docs: finalize 0.2.0 changelog and correct 0.1.4 date ... CBOR is the headline 0.2.0 feature, not 0.1.4: at v0.1.4 serial.nim was still JSON/string-based, so the prior CBOR attribution was wrong. Also complete the 0.2.0 scope (events, registry, codegen) ahead of tagging. Date 0.1.4 by its last functional change (#14, 2026-05-13) rather than the later changelog/version-bump commits, so the version reflects when its code actually settled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 09:17:56 +02:00
Ivan FB	11aae0c7b8	add changelog for 0.1.4 (#73)	2026-06-03 23:43:52 +02:00
Ivan FB	5e6e58e7d1	Increase version to v0.2.0 (#37)	2026-05-21 16:33:38 +02:00