-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
add Key()
method to the Handler
concept
#134
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
57e1c87
add `Key()` method to the `Handler` concept
Kosta-Github 17b1a14
add `Key()` method to `Writer` and `PrettyWriter`
Kosta-Github 23b3d24
add `Key()` to IterativeParsingReaderHandler` in `readertest.cpp`
Kosta-Github 0f40710
fix `simplereader.cpp` and the `Key()->String()` forwarding in `BaseR…
Kosta-Github c8da4d8
add `Key()->String()` forwarding to the `capitalize` example
Kosta-Github 8b2faff
enhance `IterativeParsingReaderHandler` to check for `Key()` events
Kosta-Github 25f4892
removed unused argument names
Kosta-Github 4a71dc6
reunified `ParseKey`, `ParseString`, and `ParseStringOrKey` again
Kosta-Github e70494b
fix for `Reader::ParseString()` implementation plus some minor code c…
Kosta-Github 00ac102
more changes
Kosta-Github f0d9ab4
finally fixing `Reader::ParseString()`
Kosta-Github 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 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 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 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 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 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 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 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
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.
Adding duplicate code via a template parameter will lead to binary bloat due to the duplicate implementation for each instantiated
parseFlags
value. I would prefer a parameter toParseStringOrKey
(it's internal anyway).Why not simply keep it as
ParseString
and add an optional flag: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.
based on all the other templated stuff in that file I think you guys are aiming for absolute runtime performance; therefore I chose the template
bool
parameter over the "runtime"bool
parameter passed as regular argument...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.
It's always a tradeoff. The increased program size will lead to I$ pressure for a very small anticipated performance benefit.