-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
don't bother caching if we're using a nil repo #5414
Conversation
(it'll be wrong anyways) License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
} | ||
|
||
wbs = bstore.NewIdStore(wbs) | ||
bs = bstore.NewIdStore(bs) |
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.
I renamed this (made it slightly harder to disable caching). Any reason it was wbs
?
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.
That's fine.
@Stebalien what's the motivation for this change. When is a nil repo used? |
When adding files with |
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.
I don't fully understand the reasons for this but I don't see the harm.
LGTM.
The main reasons are:
In practice, given where we use the nil repo, this really shouldn't make much of a difference (maybe a slight performance gain). |
(it'll be wrong anyways)