LibGit2 miscellaneous fixes to credential callback#20751
Conversation
|
where's the type instability here? is doing |
|
Type instability was that |
Probably not, I didn't do performance tests between the two. Is there an issue with adding in the |
|
same as other kinds of conditional compilation, you could have invalid code in the inactive branch and possibly not notice until you send things through appveyor |
|
I didn't consider that. Since we always test with appveyor though the invalid code will eventually get caught. I personally would still leave in the |
|
appveyor doesn't help people testing locally, I'd rather use |
|
What's the kind of error you want to catch by removing |
|
I understand your point and agree in principle, @tkelman, but it seems pretty harmless in this case. (At least it seems that way to me.) I have no strong feelings either way I suppose, but the rest of this PR looks good to me. |
|
Deprecations, as one example Unless you're actually looking at the appveyor log every time, that stuff can slip through until someone who actually builds on windows (usually me) notices and fixes it. If |
6d3e691 to
35321e7
Compare
|
I've reverted the |
Part of #20725.
nothingchecks againstStrings.errvariable.Uses@staticto avoid runtime calls tois_windows