User classes expose typed-signal API even without #[signal]
#1146
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, you needed at least one
#[signal]to make yourGodotClasseligible for theWithUserSignalstrait, meaning otherwise you couldn't accessself.signals()orGd::signals()methods. This made sense while at the time, but with implicit access to base signals, this can now be relaxed.The new rule is: typed signals are enabled if your class has a
Base<T>field. This still allows to use lightweight data classes without base fields.This PR also provides a blanked opt-out for typed signals:
This should be rarely needed, but can be helpful in situations where proc-macro API causes problems (e.g.
impl nested::MyClass) or excessive code generation. If enabled,#[signal]can still be used and will register the signal, but not generate any typed APIs -- just like in v0.2.