perf: avoid protocol registry redundant lookup #41991
Merged
+53
−51
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.
Description of Change
Fix a performance wart in
ProtocolRegistry
. The current workflow is to callProtocolRegistry::handlers().at(scheme)
after a safeguard check toProtocolRegistry::IsRegistered(scheme)
. This workflow requires a redundant lookup forscheme
and is also a minor demeter violation.This PR replaces the methods
ProtocolRegistry::IsRegistered(scheme)
andProtocolRegistry::handlers(scheme)
with a newProtocolRegistry::FindRegistered(scheme) const
that returns a const pointer to the handler, ornullptr
if none is found.Checklist
npm test
passesRelease Notes
Notes: none