> I'd love to contribute, but I simply don't have enough knowledge. I don't > know how gintro works or it is organized. I am NOT a programmer. Programming > is my hobby.
Actually, what you are currently trying is much more difficult than fixing a tiny gintro issue. Working with GObject GLists from other languages with automatic garbage collection is hard, one has to study API docs or GIR files to know who owns the lists and who owns the elements, and then care for memory deallocation or to keep things alive. I would recommend you to copy the data from the GList to a Nim seq early, then free GList and elements when necessary, and continue with Nim seq. That is how gintro does it. The Rust bindings may do all that in a much smarter way, but the rust guys are much brighter than me, and there are a few of then.
