dumblob

Ah, ok. This reminds me of Nim's references. Now it's clear that it should be easy to judge about the source code whether we're dealing with "dangerous pointers" or "safe...

This sounds awesome! This type of FFI would be a static/compile-time/AOT offering high performance. In addition to that I'd also welcome support for runtime execution of Python ecosystem. As crazy...

> Similar to [Go's primitive int types](https://tour.golang.org/basics/11), I propose redefining the current `Int` type as a generic "best size" integer type equal to the word size of the target architecture....

Nuklear development moved under an [organization](https://github.com/Immediate-Mode-UI/Nuklear ) and there is a new [Android example](https://github.com/Immediate-Mode-UI/Nuklear/pull/413 ).

Just a note that not all references has to be garbage collected - some (and practice in programming in [V](https://vlang.io/ ) shows there'll be many - incl. smaller arrays &...

> I'm a bit dubious of any result coming from V... :rofl: >but yes, Basil will remain unboxed by default. :+1: This is important. >These will behave primarily like OCaml's...

https://github.com/matthieu-m/static-rc - yet another small step towards lower reference counting pressure.

> but I'd like to explore some sophisticated escape analysis in the future. Lifetime analysis during optimization and potentially some alternative kinds of dynamic allocation (like on-stack mini-arenas) are potentially...

Just saw an interesting take on reference counting with less than half the overhead of "traditional" optimized RC. https://verdagon.dev/blog/generational-references https://verdagon.dev/blog/hybrid-generational-memory Might be interesting to explore in the context of Basil.

I agree with @paulfitz . OTOH if your needed something super simple and quick, http://demo.bpmn.io/form might be the way to go.