Marcel Tiede

Improved Concept: Use Static methods and generics to Throw an exception. This avoids list allocations and looping at all. Similar things are done [here](https://github.com/gircore/gir.core/blob/d57343b70abe30fe50a462e19310f3c36091c644/src/Extensions/GObject-2.0.Integration/SourceAnalyzer/Analyzer.cs#L22). The following code must be generated:...

Can Confirm on Fedora 40.

Another idea would be to add [annotations upstream](https://gitlab.gnome.org/GNOME/gobject-introspection/-/blob/main/docs/gir-1.2.rnc#L529) so other bindings can benefit and do not need to add heuristics, too.

My philosophy is to do it on a case by case basis. I started adding some `ref-func` annotations [upstream](https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4161#note_2192105) because my project would benefit from it. If some async function...

I merged #1093 to support better logging for this scenario.

Can you provide a link to the msvc packages? Your request was already made but the issue got resolved differently: https://github.com/gircore/gir.core/issues/963 If there is another package registry providing msvc builds...

I wonder if it makes more sense to create an DllInportResolver interface and allow to replace the import resolver completely in each module. So the ImportResolver would not be static...

Actually you can call api in the "Internal" namespace. All classes in there are public by design. This is to allow to work around missing bindings or bugs. Only be...

Sorry for the missinformation. I did not verify my assumptions.

For details about the breaking changes in GirCore please see the release notes of version [0.6.2](https://github.com/gircore/gir.core/releases/tag/0.6.2). There are explanations and migration hints.