-
Notifications
You must be signed in to change notification settings - Fork 99
Update the KafkaException using modern practices #241
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
Open
downfa11
wants to merge
5
commits into
morganstanley:main
Choose a base branch
from
downfa11:main
base: main
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
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d117f9c
Refactor kafkaException constructor
downfa11 b0793aa
Refactor kafkaException constructor
downfa11 f39a4fb
Merge branch 'main' of https://github.com/downfa11/modern-cpp-kafka
downfa11 0e3a826
refactor: Replace exception macros with source_location
downfa11 dfd6121
Removed KafkaException dependencies
downfa11 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
std::source_locationis quit an elegant choice, but it's not supported until c++20. (the project has to be compatible with c++14/17)std::source_locationas the default parameter, we could get rid of the macroKAFKA THROW_ERRORas well -- justthrow KafkaException(error)at where we need it.Uh oh!
There was an error while loading. Please reload this page.
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.
Thanks for the feedback!
As far as I know,
source_locationwas originally provided in Boost before being adopted into C++20.Since project already depends on Boost (e.g., for
boost::optional), usingboost::source_locationwill not introduce any new external dependencies.I also plan to update the code so that exceptions can be thrown directly via
KafkaException(error)and remove theKAFKA_THROW_ERRORmacro in the process.What do you think?
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.
Yes, we have to use some trick for the
optional, -- https://github.com/morganstanley/modern-cpp-kafka/blob/main/include/kafka/Types.h#L19It also make the dependencies messy, https://github.com/morganstanley/modern-cpp-kafka/blob/main/.github/workflows/kafka_api_ci_tests.yml#L307
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.
While the
boost::source_location solutionis certainly elegant, I'm wondering if introducing a new Boost dependency might be a concern for the project.I'd like to make sure we aren't adding complexity where we're trying to remove it.