-
Notifications
You must be signed in to change notification settings - Fork 273
C library: handle side effects of scanf #7369
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
Conversation
Codecov ReportBase: 78.34% // Head: 78.35% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #7369 +/- ##
===========================================
+ Coverage 78.34% 78.35% +0.01%
===========================================
Files 1644 1645 +1
Lines 190313 190190 -123
===========================================
- Hits 149097 149031 -66
+ Misses 41216 41159 -57
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Recent glibc uses these names.
MSVC headers eventually call these when using fscanf/sscanf.
c7aaec3
to
b15002b
Compare
scanf may write to any of the objects behind the pointer-typed arguments.
This is to ensure git-clang-format doesn't end up confused and spuriously starts indenting from the closing curly brace of vsscanf onwards.
b15002b
to
a165746
Compare
Please review commit-by-commit.