Update to signals chapter #96
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bromeon
force-pushed
the
feature/signals-update
branch
2 times, most recently
from
1c1aa96 to
3c9b95a
Compare
Bromeon
force-pushed
the
feature/signals-update
branch
from
3c9b95a to
86dc3c6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Incorporates newer information to signals from various recent PRs:
emit()now available on inherited symbols + smaller cleanups gdext#1135#[signal]gdext#1146emit()functions now takeimpl AsArg<T>gdext#1150connect*usage gdext#1152ConnectBuilderand some other signal APIs gdext#1171ConnectBuilder::connect_*_gd()takesGdinstead of&mut Gdgdext#1175IndirectSignalReceiverto force type inference to work when connecting closures to the signals gdext#1179