Revision tags: llvmorg-18.1.8, llvmorg-18.1.7 |
|
#
1c58208d |
| 21-May-2024 |
Owen Pan <owenpiano@gmail.com> |
[clang-format][NFC] Remove redundnat llvm::, clang::, etc.
|
Revision tags: llvmorg-18.1.6, llvmorg-18.1.5, llvmorg-18.1.4, llvmorg-18.1.3 |
|
#
b2082a98 |
| 20-Mar-2024 |
Owen Pan <owenpiano@gmail.com> |
Revert "[clang-format][NFC] Delete 100+ redundant #include lines in .cpp files"
This reverts commit b92d6dd704d789240685a336ad8b25a9f381b4cc. See github.com/llvm/llvm-project/commit/b92d6dd704d7#com
Revert "[clang-format][NFC] Delete 100+ redundant #include lines in .cpp files"
This reverts commit b92d6dd704d789240685a336ad8b25a9f381b4cc. See github.com/llvm/llvm-project/commit/b92d6dd704d7#commitcomment-139992444
We should use a tool like Visual Studio to clean up the headers.
show more ...
|
Revision tags: llvmorg-18.1.2 |
|
#
b92d6dd7 |
| 17-Mar-2024 |
Owen Pan <owenpiano@gmail.com> |
[clang-format][NFC] Delete 100+ redundant #include lines in .cpp files
|
Revision tags: llvmorg-18.1.1, llvmorg-18.1.0, llvmorg-18.1.0-rc4, llvmorg-18.1.0-rc3, llvmorg-18.1.0-rc2, llvmorg-18.1.0-rc1, llvmorg-19-init |
|
#
f3dcc235 |
| 13-Dec-2023 |
Kazu Hirata <kazu@google.com> |
[clang] Use StringRef::{starts,ends}_with (NFC) (#75149)
This patch replaces uses of StringRef::{starts,ends}with with
StringRef::{starts,ends}_with for consistency with
std::{string,string_view}:
[clang] Use StringRef::{starts,ends}_with (NFC) (#75149)
This patch replaces uses of StringRef::{starts,ends}with with
StringRef::{starts,ends}_with for consistency with
std::{string,string_view}::{starts,ends}_with in C++20.
I'm planning to deprecate and eventually remove
StringRef::{starts,ends}with.
show more ...
|
Revision tags: llvmorg-17.0.6, llvmorg-17.0.5, llvmorg-17.0.4 |
|
#
265ed681 |
| 25-Oct-2023 |
Owen Pan <owenpiano@gmail.com> |
[clang-format] Fix a JavaScript import order bug
When the imported symbol is exactly "template" the sorting is disabled. "import {template} from x;" is not recognized as an import.
Differential Rev
[clang-format] Fix a JavaScript import order bug
When the imported symbol is exactly "template" the sorting is disabled. "import {template} from x;" is not recognized as an import.
Differential Revision: https://reviews.llvm.org/D61663
show more ...
|
Revision tags: llvmorg-17.0.3, llvmorg-17.0.2, llvmorg-17.0.1, llvmorg-17.0.0, llvmorg-17.0.0-rc4 |
|
#
91c4db00 |
| 24-Aug-2023 |
Owen Pan <owenpiano@gmail.com> |
[clang-format][NFC] Replace !is() with isNot()
Differential Revision: https://reviews.llvm.org/D158571
|
Revision tags: llvmorg-17.0.0-rc3, llvmorg-17.0.0-rc2, llvmorg-17.0.0-rc1, llvmorg-18-init |
|
#
5942ae86 |
| 27-Jun-2023 |
Sindhu Chittireddy <sindhu.chittireddy@intel.com> |
[NFC] Initialize class member pointers to nullptr.
Reviewed here: https://reviews.llvm.org/D153926
|
Revision tags: llvmorg-16.0.6, llvmorg-16.0.5, llvmorg-16.0.4 |
|
#
e1f34b73 |
| 15-May-2023 |
Jan Kuhle <jankuehle@google.com> |
clang-format: [JS] terminate import sorting on `export type X = Y`
Contributed by @jankuehle!
https://reviews.llvm.org/D150116 introduced a bug. `export type X = Y` was considered an export declara
clang-format: [JS] terminate import sorting on `export type X = Y`
Contributed by @jankuehle!
https://reviews.llvm.org/D150116 introduced a bug. `export type X = Y` was considered an export declaration and took part in import sorting. This is not correct. With this change `export type X = Y` properly terminates import sorting.
Reviewed By: krasimir
Differential Revision: https://reviews.llvm.org/D150563
show more ...
|
#
34b422ba |
| 10-May-2023 |
Jan Kuhle <jankuehle@google.com> |
clang-format: [JS] support import/export type
Contributed by @jankuehle!
Users can choose to only import/export the type of the symbol (not value nor namespace) by adding a `type` keyword, e.g.:
`
clang-format: [JS] support import/export type
Contributed by @jankuehle!
Users can choose to only import/export the type of the symbol (not value nor namespace) by adding a `type` keyword, e.g.:
``` import type {x} from 'y'; import {type x} from 'y'; export type {x}; export {type x}; ```
Previously, this was not handled and would: - Terminate import sorting - Remove the space before the curly bracket in `export type {`
With this change, both formatting and import sorting work as expected.
Reviewed By: MyDeveloperDay, krasimir
Differential Revision: https://reviews.llvm.org/D150116
show more ...
|
Revision tags: llvmorg-16.0.3, llvmorg-16.0.2, llvmorg-16.0.1, llvmorg-16.0.0, llvmorg-16.0.0-rc4, llvmorg-16.0.0-rc3, llvmorg-16.0.0-rc2 |
|
#
25e2d0f3 |
| 28-Jan-2023 |
Owen Pan <owenpiano@gmail.com> |
[clang-format] Support clang-format on/off line comments as prefix
Closes #60264.
Differential Revision: https://reviews.llvm.org/D142804
|
Revision tags: llvmorg-16.0.0-rc1, llvmorg-17-init, llvmorg-15.0.7, llvmorg-15.0.6, llvmorg-15.0.5, llvmorg-15.0.4, llvmorg-15.0.3, working, llvmorg-15.0.2, llvmorg-15.0.1, llvmorg-15.0.0, llvmorg-15.0.0-rc3, llvmorg-15.0.0-rc2, llvmorg-15.0.0-rc1, llvmorg-16-init, llvmorg-14.0.6, llvmorg-14.0.5, llvmorg-14.0.4 |
|
#
bebf7bdf |
| 22-May-2022 |
owenca <owenpiano@gmail.com> |
[clang-format][NFC] Insert/remove braces in clang/lib/Format/
Differential Revision: https://reviews.llvm.org/D126157
|
Revision tags: llvmorg-14.0.3, llvmorg-14.0.2, llvmorg-14.0.1, llvmorg-14.0.0, llvmorg-14.0.0-rc4, llvmorg-14.0.0-rc3, llvmorg-14.0.0-rc2, llvmorg-14.0.0-rc1 |
|
#
d079995d |
| 02-Feb-2022 |
Marek Kurdej <marek.kurdej+llvm.org@gmail.com> |
[clang-format] Elide unnecessary braces. NFC.
|
Revision tags: llvmorg-15-init |
|
#
c2672925 |
| 28-Jan-2022 |
Martin Probst <martin@probst.io> |
clang-format: [JS] fix uninitialized memory.
SortJavaScriptImports attempts to set its currently parsed token to an invalid token when it reaches the end of the line. However in doing so, it used a
clang-format: [JS] fix uninitialized memory.
SortJavaScriptImports attempts to set its currently parsed token to an invalid token when it reaches the end of the line. However in doing so, it used a `FormatToken`, which contains a `Token Tok`. `Token` does not have a constructor, so its fields start out as uninitialized memory.
`Token::startToken()` initializes all fields. Calling it in `JavaScriptImportSorter`'s constructor thus fixes the problem.
Differential Revision: https://reviews.llvm.org/D118448
show more ...
|
#
03c59765 |
| 28-Jan-2022 |
Martin Probst <martin@probst.io> |
clang-format: [JS] sort import aliases. Users can define aliases for long symbols using import aliases:
import X = A.B.C;
Previously, these were unhandled and would terminate import sorting. Wi
clang-format: [JS] sort import aliases. Users can define aliases for long symbols using import aliases:
import X = A.B.C;
Previously, these were unhandled and would terminate import sorting. With this change, aliases sort as their own group, coming last after all other imports.
Aliases are not sorted within their group, as they may reference each other, so order is significant.
This reverts commit f750c3d95a0c8bf1d21380ae753fce12010a7561. It fixes the msan issue by not parsing past the end of the line when handling import aliases.
Differential Revision: https://reviews.llvm.org/D118446
show more ...
|
#
f750c3d9 |
| 28-Jan-2022 |
Vitaly Buka <vitalybuka@google.com> |
Revert "clang-format: [JS] sort import aliases."
Triggers MSAN report.
This reverts commit c6d5efb5d98093c4bd7578b2ea52c9032d20dea3.
|
#
c6d5efb5 |
| 27-Jan-2022 |
Martin Probst <martin@probst.io> |
clang-format: [JS] sort import aliases.
Users can define aliases for long symbols using import aliases:
import X = A.B.C;
Previously, these were unhandled and would terminate import sorting. W
clang-format: [JS] sort import aliases.
Users can define aliases for long symbols using import aliases:
import X = A.B.C;
Previously, these were unhandled and would terminate import sorting. With this change, aliases sort as their own group, coming last after all other imports.
Aliases are not sorted within their group, as they may reference each other, so order is significant.
Revision URI: https://reviews.llvm.org/D118361
show more ...
|
#
670a721d |
| 24-Jan-2022 |
Marek Kurdej <marek.kurdej+llvm.org@gmail.com> |
[clang-format] Assert Line->First. NFC.
Cf. scan-build reports: * https://llvm.org/reports/scan-build/report-AffectedRangeManager.cpp-nonPPLineAffected-34-16c04b.html#EndPath * https://llvm.org/repo
[clang-format] Assert Line->First. NFC.
Cf. scan-build reports: * https://llvm.org/reports/scan-build/report-AffectedRangeManager.cpp-nonPPLineAffected-34-16c04b.html#EndPath * https://llvm.org/reports/scan-build/report-SortJavaScriptImports.cpp-parseModuleReferences-34-96a7f8.html#EndPath * https://llvm.org/reports/scan-build/report-TokenAnnotator.cpp-setCommentLineLevels-26-77bdba.html#EndPath * https://llvm.org/reports/scan-build/report-AffectedRangeManager.cpp-nonPPLineAffected-31-714434.html#EndPath * https://llvm.org/reports/scan-build/report-TokenAnnotator.cpp-setCommentLineLevels-16-bd39d0.html#EndPath * https://llvm.org/reports/scan-build/report-UnwrappedLineFormatter.cpp-format-90-668b2d.html#EndPath
show more ...
|
Revision tags: llvmorg-13.0.1, llvmorg-13.0.1-rc3, llvmorg-13.0.1-rc2 |
|
#
4681ae93 |
| 07-Jan-2022 |
Marek Kurdej <marek.kurdej+llvm.org@gmail.com> |
[clang-format] Use range-for loops. NFC.
* Avoid if check on every element of the loop when printing symbols.
|
#
359b4e6c |
| 07-Jan-2022 |
Marek Kurdej <marek.kurdej+llvm.org@gmail.com> |
[clang-format] Use prefix increment and decrement. NFC.
|
#
93fc9161 |
| 24-Nov-2021 |
mydeveloperday <mydeveloperday@gmail.com> |
[clang-format] NFC - recent changes caused clang-format to no longer be clang-formatted.
The following 2 commits caused files in clang-format to no longer be clang-formatted.
we would lose our "cle
[clang-format] NFC - recent changes caused clang-format to no longer be clang-formatted.
The following 2 commits caused files in clang-format to no longer be clang-formatted.
we would lose our "clean" status https://releases.llvm.org/13.0.0/tools/clang/docs/ClangFormattedStatus.html
c2271926a4fc - Make clang-format fuzz through Lexing with asserts enabled (https://github.com/llvm/llvm-project/commit/c2271926a4fc )
84bf5e328664 - Fix various problems found by fuzzing. (https://github.com/llvm/llvm-project/commit/84bf5e328664)
Reviewed By: HazardyKnusperkeks, owenpan
Differential Revision: https://reviews.llvm.org/D114430
show more ...
|
Revision tags: llvmorg-13.0.1-rc1 |
|
#
c2271926 |
| 19-Nov-2021 |
Manuel Klimek <klimek@google.com> |
Make clang-format fuzz through Lexing with asserts enabled.
Makes clang-format bail out if an in-memory source file with an unsupported BOM is handed in instead of creating source locations that are
Make clang-format fuzz through Lexing with asserts enabled.
Makes clang-format bail out if an in-memory source file with an unsupported BOM is handed in instead of creating source locations that are violating clang's assumptions.
In the future, we should add support to better transport error messages like this through clang-format instead of printing to stderr and not creating any changes.
show more ...
|
Revision tags: llvmorg-13.0.0, llvmorg-13.0.0-rc4, llvmorg-13.0.0-rc3, llvmorg-13.0.0-rc2, llvmorg-13.0.0-rc1, llvmorg-14-init, llvmorg-12.0.1, llvmorg-12.0.1-rc4, llvmorg-12.0.1-rc3 |
|
#
e5c7c171 |
| 23-Jun-2021 |
Martin Storsjö <martin@martin.st> |
[clang] Rename StringRef _lower() method calls to _insensitive()
This is mostly a mechanical change, but a testcase that contains parts of the StringRef class (clang/test/Analysis/llvm-conventions.c
[clang] Rename StringRef _lower() method calls to _insensitive()
This is mostly a mechanical change, but a testcase that contains parts of the StringRef class (clang/test/Analysis/llvm-conventions.cpp) isn't touched.
show more ...
|
Revision tags: llvmorg-12.0.1-rc2 |
|
#
63042d46 |
| 11-Jun-2021 |
Martin Probst <martin@probst.io> |
clang-format: [JS] don't sort named imports if off.
The previous implementation would accidentally still sort the individual named imports, even if the module reference was in a clang-format off blo
clang-format: [JS] don't sort named imports if off.
The previous implementation would accidentally still sort the individual named imports, even if the module reference was in a clang-format off block.
Differential Revision: https://reviews.llvm.org/D104101
show more ...
|
Revision tags: llvmorg-12.0.1-rc1 |
|
#
b2780cd7 |
| 29-Apr-2021 |
Martin Probst <martin@probst.io> |
clang-format: [JS] handle "off" in imports
Previously, the JavaScript import sorter would ignore `// clang-format off` and `on` comments. This change fixes that. It tracks whether formatting is enab
clang-format: [JS] handle "off" in imports
Previously, the JavaScript import sorter would ignore `// clang-format off` and `on` comments. This change fixes that. It tracks whether formatting is enabled for a stretch of imports, and then only sorts and merges the imports where formatting is enabled, in individual chunks.
This means that there's no meaningful total order when module references are mixed with blocks that have formatting disabled. The alternative approach would have been to sort all imports that have formatting enabled in one group. However that raises the question where to insert the formatting-off block, which can also impact symbol visibility (in particular for exports). In practice, sorting in chunks probably isn't a big problem.
This change also simplifies the general algorithm: instead of tracking indices separately and sorting them, it just sorts the vector of module references. And instead of attempting to do fine grained tracking of whether the code changed order, it just prints out the module references text, and compares that to the previous text. Given that source files typically have dozens, but not even hundreds of imports, the performance impact seems negligible.
Differential Revision: https://reviews.llvm.org/D101515
show more ...
|
#
fbc6f42d |
| 22-Apr-2021 |
Martin Probst <martin@probst.io> |
clang-format: [JS] do not merge side-effect imports.
The if condition was testing the current element, but forgot to check the previous element (doh), so it would fail depending on sort order of the
clang-format: [JS] do not merge side-effect imports.
The if condition was testing the current element, but forgot to check the previous element (doh), so it would fail depending on sort order of the imports.
Differential Revision: https://reviews.llvm.org/D101020
show more ...
|