[ThinLTO] Extract optionality out of ModuleCacheEntry
#8083
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
All existing kinds of `ModuleCacheEntry` contain the same kind of optionality: their `getEntryPath()`, `tryLoadingBuffer()` and `write()` functions are no-op if the ThinLTO key could not be computed in their constructors. This patch extracts the concept of no-op cache entry into `NullModuleCacheEntry`, simplifying the logic.
cachemeifyoucan
approved these changes
Jan 30, 2024
|
Thanks! I'll squash when merging. |
jansvoboda11
added a commit
that referenced
this pull request
Apr 19, 2024
All existing kinds of `ModuleCacheEntry` contain the same kind of optionality: their `getEntryPath()`, `tryLoadingBuffer()` and `write()` functions are no-op if the ThinLTO key could not be computed in their constructors. This patch extracts the concept of no-op cache entry into `NullModuleCacheEntry`, simplifying the logic. (cherry picked from commit b168a63)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
All existing kinds of
ModuleCacheEntrycontain the same kind of optionality: theirgetEntryPath(),tryLoadingBuffer()andwrite()functions are no-op if the ThinLTO key could not be computed in their constructors.This patch extracts the concept of no-op cache entry into
NullModuleCacheEntry, simplifying the logic.