-
-
Notifications
You must be signed in to change notification settings - Fork 31
SocketListener::accept_async panics #99
Comments
Gir don't look at this attribute at all, only at |
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). |
For now maybe just implement this specific function manually? |
@antoyo What's the status here? Is there still a problem, and if so can you provide a testcase to reproduce it? |
It is. Fixing |
See #221 |
Hi.
The current
SocketListener::accept_async
method does not work because theObject
parameter of the callback should be optional (and the.gir
file says so) but it is not.It might be because
gir
does not look at theoptional
attribute when generating the callback.The text was updated successfully, but these errors were encountered: