Implement a memory safe way to connect signals. #152
Conversation
This file contains 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
|
This POC doesn't handle parameters others than primitive types... nothing really hard to implement, but require a bit of time to do so... anyway, it's on my queue. |
hugopl
changed the title
hugopl
changed the title
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.
Fixes #150
I'll try to port Tijolo to this API, if everything works then I can merge this.
After merge this, there will only one more release before tag the .connect methods deprecated.
I need to write more tests... e.g. signals that return values doesn't work because the connect macro doesn't have return value information.
I also need to add more user friendly compiler error messages... anyway, it looks good for a POC.