- Notifications
You must be signed in to change notification settings - Fork2.5k
config: removefree
ptr fromgit_config_entry
#6804
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
This is a leftover leaky abstraction. If consumers aren't meant to_call_ the `free` function then they shouldn't _see_ the free function.Move it out into a `git_config_backend_entry` that is, well, produced bythe config backends.This makes our code messier but is an improvement for consumers.
bd72fd5
toaa093c4
CompareSign up for freeto 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.
While looking at the documentation, it became clear that the
git_config_entry
function was strange...This is a leftover leaky abstraction. If consumers aren't meant tocall the
free
function then they shouldn'tsee the free function. Move it out into agit_config_backend_entry
that is, well, produced by the config backends.This makes our code messier but is an improvement for consumers.