Godot version:
3.1 beta 4
OS/device including version:
Windows 10
Issue description:
You can't add typing to signals. This was probably a missed thing when implementing typing.
11clock
All 4 comments
This is not a bug, it was deliberately not implemented. Typing for signals require much more thought than regular typing for variables and methods.
I thought there was an issue about this already, but couldn't find in a quick search.
vnen
on 19 Feb 2019
are you gonna target it for 3.2?
MustaphaRashiduddin
on 20 Feb 2019
Since this has come up again, let me clarify that the reason that I didn't add typing for signals is that it's difficult to enforce in the compiler. Since signals use strings and variables to connect and emit, it's harder to track the origin of the signal and connected function.
Once we add first-class functions we'll be able to connect directly using a function reference, then it'll be easier to track and enforce the typing rules in signals.
vnen
on 14 May 2019
please add this there is no point in staticly typing if we can use it for everything
I would also like to see this supported for custom types for 4.0
Shadowblitz16
on 21 Sep 2020
Related issues
Zylann
路
3Comments
nunodonato
路
3Comments
ndee85
路
3Comments
blurymind
路
3Comments
ducdetronquito
路
3Comments
Most helpful comment
Since this has come up again, let me clarify that the reason that I didn't add typing for signals is that it's difficult to enforce in the compiler. Since signals use strings and variables to connect and emit, it's harder to track the origin of the signal and connected function.
Once we add first-class functions we'll be able to connect directly using a function reference, then it'll be easier to track and enforce the typing rules in signals.