Mike Gran

`tree-store:set` does also appear to work; however, the Scheme API is also torturous. See c8908fd92e1eaab5959772bfdfd98db299ae0c23 `guile-gi` definitely needs more flexible handling of `GArray` . Requiring bytevectors is inflexible.

From what I gather from the developer blogs, list views and models and associated classes are quite different in Gtk4. Perhaps they will be better supported

Well, I can take another look, but, the core problem is that guile-gi only provides functionality that the introspection library provides, and it doesn't provide any exceptional work-arounds except for...

@ZelphirKaltstahl Email is perfectly fine by me, but if you want to do it on a web site, i enabled the discussions tab in GitHub. I've never used it tho,...

So it appears that in the GIR and Typelib files, all of the GHashTable constructors are marked as not introspectable, so there is no way to construct a GHashTable via...

I've implemented a minimal interface. It is primitive, but, it provides the minimum functionality and tracks the C API. I'm not sure about what higher-level API would be appropriate, since...

These patches always convert a Guile hashtable to a `GHashTable` and vice versa as required by a function call. OUT and INOUT are handled correctly. The next problem is that...

I talked to the g-golf maintainer, who himself has talked to the GObject Introspection about the duplication between GIArgument and GValue. Apparently they feel there is too much technical debt...

Previously, there was the `LATER_FREE` mechanism used to free temporary variables created during argument marshalling, and this worked because those temp variables were created using a `malloc` analog, and the...

`GBytes` could just be unpacked as a bytevector, but, it has the added wrinkle that its contents are supposed to be read only. Since there is no such thing as...