log: drop specialization of boost::lexical_cast for log_level#2570
Closed
avikivity wants to merge 1 commit intoscylladb:masterfrom
Closed
log: drop specialization of boost::lexical_cast for log_level#2570avikivity wants to merge 1 commit intoscylladb:masterfrom
avikivity wants to merge 1 commit intoscylladb:masterfrom
Conversation
log.hh contains a declaration of a specializtion of lexical_cast for log_level, noting boost doesn't pick up operator<< for log_level, but everything seems to work without the specialization. Dropping it means we can drop yet another boost dependency in a commonly used header file, one that pulls in much of the boost.ranges core.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
log.hh contains a declaration of a specializtion of lexical_cast for log_level, noting boost doesn't pick up operator<< for log_level, but everything seems to work without the specialization. Dropping it means we can drop yet another boost dependency in a commonly used header file, one that pulls in much of the boost.ranges core.