Rename cache to pool #1
Closed
Conversation
This file contains 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
skaldarnar
approved these changes
Jul 5, 2017
|
Not much to review, go ahead and merge it 👍 |
|
Merged in MovingBlocks#3009 |
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.
This PR renames all instances of 'cache' to 'pool,' which is a more suitable name.
'Cache,' especially when related to computing, implies some form of saving/caching against a separate main store, which is not what they are doing. I think that 'pool' (suggested by @Cervator) is a more appropriate name, because all they are doing is splitting up the entity storage into multiple smaller, independent groups.