We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As of https://reviews.llvm.org/D93839, clang-format can produce different formatted files depending on amount of whitespace. For example, given (A):
#include <stdint.h> namespace fuzzing {}
clang-format with this patch would produced (B):
clang-format
#include <stdint.h> namespace fuzzing { }
but given (C):
would be formatted to (D):
The invocation specifically is clang-format --style=google file. Prior to this patch, both inputs (A/C) would give the same output:
clang-format --style=google file
This seems to be unintended behavior that should be fixed. This doesn't seem to occur if #include "stdint.h" is used.
#include "stdint.h"
The text was updated successfully, but these errors were encountered:
https://reviews.llvm.org/D95479
Committed in https://reviews.llvm.org/rGe3713f156b8cb65a2b74f150afb824ce1e2a2fab.
Sorry, something went wrong.
Reopening until it gets merged into 12.x.
Merged: 0a32d93
mentioned in issue #48246
No branches or pull requests
Extended Description
As of https://reviews.llvm.org/D93839, clang-format can produce different formatted files depending on amount of whitespace. For example, given (A):
clang-format
with this patch would produced (B):but given (C):
would be formatted to (D):
The invocation specifically is
clang-format --style=google file
. Prior to this patch, both inputs (A/C) would give the same output:This seems to be unintended behavior that should be fixed. This doesn't seem to occur if
#include "stdint.h"
is used.The text was updated successfully, but these errors were encountered: