-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding exception type for empty callback functions #301
Open
gregmedd
wants to merge
4
commits into
eclipse-uprotocol:v1.0_up-v1.6.0
Choose a base branch
from
gregmedd:bugfix/1.0.2/194-std-function-checks
base: v1.0_up-v1.6.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Adding exception type for empty callback functions #301
gregmedd
wants to merge
4
commits into
eclipse-uprotocol:v1.0_up-v1.6.0
from
gregmedd:bugfix/1.0.2/194-std-function-checks
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 exception will be thrown when an empty std::function is passed to the callback connection module. Adding the type first so that tests can be written.
Code coverage report is ready! 📈
|
Code coverage report is ready! 📈
|
Some L2 tests were asserting that the std::bad_function_call exception should be thrown when a bad callback is called. We will be changing that behavior so that the exception is thrown when the callback connection is established, requiring updated test cases.
The CalleeHandle class is the "owner" of the callback function objects associated with a callback connection. As such, it will check the validity of those function objects and throw the EmptyFunctionObject exception if either the callback or cleanup function is empty / invalid.
Code coverage report is ready! 📈
|
gregmedd
requested review from
billpittman,
stevenhartley,
PLeVasseur and
agosh01
August 17, 2024 03:04
Code coverage report is ready! 📈
|
agosh01
approved these changes
Aug 17, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
This exception will be thrown when an empty std::function is passed to the callback connection module. Adding the type first so that tests can be written.
closes #194