-
Notifications
You must be signed in to change notification settings - Fork 18
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 single instance for retrieving a buffer label #214
Conversation
Check-perf-impact results: (7a518c63eb0655471fea6a4902fc0af7) ❓ No new benchmark data submitted. ❓ |
a31e54f
to
6536c3b
Compare
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
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.
clang-tidy made some suggestions
Check-perf-impact results: (5a19ced85f862a00d0114dd241122462) ❓ No new benchmark data submitted. ❓ |
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 I like DRY, I'm not a fan of having debug-printing features in the buffer manager. Since this will have to be re-visited anyway when the IDAG refactoring removes buffer_manager
, I'm fine with merging this in the meantime.
This pull request is based on #211.
It adds a uniform way to retrieve a buffer label without the need to check for an empty string.
Every buffer label is formatted like:
B{buffer_id} "{buffer_name}"
.