-
Notifications
You must be signed in to change notification settings - Fork 64
Don't try to convert string if it's already an LLWString; also remove orphaned method declarations #2732
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
Closed
Closed
Don't try to convert string if it's already an LLWString; also remove orphaned method declarations #2732
Changes from all commits
Commits
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
Oops, something went wrong.
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.
Certainly we want
ll_convert<T>(const T& in)
to be a no-op. Do you observe otherwise?The design intent is to be able to use
ll_convert()
to adapt any conventional viewer string type to the intended target type, without having to break out special cases -- even if the source type is already the target type.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.
You are still having to call the operator and shuffle the strings around - unless the compiler somehow optimizes it away. This change prevents that by doing the check at compile time and omitting the no-op call of the operator.
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.
The key question seems to be whether there's zero runtime cost to a same-type
ll_convert()
. If that turns out not to be true, my preferred fix would be to try to eliminate that runtime cost.I'm happy we now have
if constexpr
; I'd hate to have to usestd::enable_if
tricks to effect the same thing. My problem with the proposed change is that it suggests propagating the same logic everywhere the source might be the same type as the target. I'd rather have a 10-character function call than a 4-line idiom.