Setting a GI function as a callback triggers an assert.
This line returns nullptr
for GIRepositoryFunction
(and presumably other function derivatives) which means we hit this assert if you do something like...
GLib.set_callback(GLib.some_function)
I discovered this when trying
GLib.log_set_writer_func(GLib.log_default_handler)
I'd assume the two solutions would be to either "wrap" these functions automatically in a JS function or to figure out passing the C function pointer directly if there aren't concerns with that.
Edited by Philip Chimento