[llvm-readtapi] Avoid repeated hash lookups (NFC) #128131
Merged
Conversation
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
Dylibs is a StringMap, which takes StringRef as the key type, so NormalizedPath.str() is good enough. We don't need to create a null terminated string. Neither do we need to recompute the string length as part of StringRef construction.
nikic
approved these changes
Feb 21, 2025
kazutakahirata
deleted the
cleanup_001_repeated_hash_lookups_llvm_readtapi
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Dylibs is a StringMap, which takes StringRef as the key type, so
NormalizedPath.str() is good enough. We don't need to create a null
terminated string. Neither do we need to recompute the string length
as part of StringRef construction.