SocketListener::accept_async panics about gio HOT 6 CLOSED

See #221

from gio.

Gir don't look at this attribute at all, only at allow-none but don't trusts him too, as many cases when it wrong.
In current realization of async trampoline IMHO will be touchcomplicated adding standard config checking as trampoline not analyzed.

from gio.

For the async trampoline we should maybe reverse the rules and assume by default that everything can be NULL unless overridden.

The problem basically is that GIR annotations exist only for "this can be NULL", but it can be easily forgotten in C libraries so the absence of that attribute does not necessarily mean that it must not be NULL / can't be NULL. So for return values we always assume that they can be NULL unless overridden in the toml file, for arguments we assume they must not be NULL unless the attribute is set (or overridden in the toml file).
What would help is a "this can not be NULL" annotation for return values.

from gio.

For now maybe just implement this specific function manually?

from gio.

@antoyo What's the status here? Is there still a problem, and if so can you provide a testcase to reproduce it?

from gio.

It is. Fixing

from gio.