maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/AST/ast-dump-template-decls-jso...

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

2709 lines
87 KiB
C++
Raw Normal View History

Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// RUN: %clang_cc1 -std=c++17 -triple x86_64-unknown-unknown -ast-dump=json %s | FileCheck -strict-whitespace %s
template <typename Ty>
void a(Ty);
template <typename... Ty>
void b(Ty...);
template <class Ty, typename Uy>
void c(Ty);
template <>
void c<float, int>(float);
template <typename Ty, template<typename> typename Uy>
void d(Ty, Uy<Ty>);
template <class Ty>
void e(Ty);
template <int N>
void f(int i = N);
template <typename Ty = int>
void g(Ty);
template <typename = void>
void h();
template <typename Ty>
struct R {};
template <>
struct R<int> {};
template <typename Ty, class Uy>
struct S {};
template <typename Ty>
struct S<Ty, int> {};
template <auto>
struct T {};
template <decltype(auto)>
struct U {};
template <typename Ty>
struct V {
template <typename Uy>
void f();
};
template <typename Ty>
template <typename Uy>
void V<Ty>::f() {}
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
template <template <typename> class = R>
void i();
Add an automated note to files produced by gen_ast_dump_json_test.py. This also details what filters, if any, were used to generate the test output. Updates all the current JSON testing files to include the automated note. llvm-svn: 364055
2019-06-21 22:37:39 +08:00
// NOTE: CHECK lines have been autogenerated by gen_ast_dump_json_test.py
[JSONNodeDumper] Regenerate test checks (NFC) gen_ast_dump_json_test.py adds these lines of whitespace. Precommit it to avoid spurious diffs in future changes.
2021-12-22 23:55:56 +08:00
[clang] Fix JSON AST output when a filter is used Without this, the combination of `-ast-dump=json` and `-ast-dump-filter FILTER` produces invalid JSON: the first line is a string that says `Dumping $SOME_DECL_NAME: `. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D108441
2021-10-10 08:44:08 +08:00
// CHECK-NOT: {{^}}Dumping
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK: "kind": "TranslationUnitDecl",
// CHECK-NEXT: "loc": {},
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TypedefDecl",
// CHECK-NEXT: "loc": {},
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__int128_t",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "__int128"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "__int128"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TypedefDecl",
// CHECK-NEXT: "loc": {},
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__uint128_t",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "unsigned __int128"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "unsigned __int128"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TypedefDecl",
// CHECK-NEXT: "loc": {},
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__NSConstantString",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "__NSConstantString_tag"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "RecordType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "__NSConstantString_tag"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "decl": {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "name": "__NSConstantString_tag"
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TypedefDecl",
// CHECK-NEXT: "loc": {},
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__builtin_ms_va_list",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "char *"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "PointerType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "char *"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "char"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TypedefDecl",
// CHECK-NEXT: "loc": {},
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {},
// CHECK-NEXT: "end": {}
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "__builtin_va_list",
// CHECK-NEXT: "type": {
Recommit: Compress formatting of array type names (int [4] -> int[4]) Based on post-commit review discussion on 2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith. Other uses of forcing HasEmptyPlaceHolder to false seem OK to me - they're all around pointer/reference types where the pointer/reference token will appear at the rightmost side of the left side of the type name, so they make nested types (eg: the "int" in "int *") behave as though there is a non-empty placeholder (because the "*" is essentially the placeholder as far as the "int" is concerned). This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075c Reverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakages outside of clang - lldb seems to have some strange/strong dependence on "char [N]" versus "char[N]" when printing strings (not due to that name appearing in DWARF, but probably due to using clang to stringify type names) that'll need to be addressed, plus a few other odds and ends in other subprojects (clang-tools-extra, compiler-rt, etc).
2021-10-15 05:52:47 +08:00
// CHECK-NEXT: "qualType": "__va_list_tag[1]"
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ConstantArrayType",
// CHECK-NEXT: "type": {
Recommit: Compress formatting of array type names (int [4] -> int[4]) Based on post-commit review discussion on 2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith. Other uses of forcing HasEmptyPlaceHolder to false seem OK to me - they're all around pointer/reference types where the pointer/reference token will appear at the rightmost side of the left side of the type name, so they make nested types (eg: the "int" in "int *") behave as though there is a non-empty placeholder (because the "*" is essentially the placeholder as far as the "int" is concerned). This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075c Reverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakages outside of clang - lldb seems to have some strange/strong dependence on "char [N]" versus "char[N]" when printing strings (not due to that name appearing in DWARF, but probably due to using clang to stringify type names) that'll need to be addressed, plus a few other odds and ends in other subprojects (clang-tools-extra, compiler-rt, etc).
2021-10-15 05:52:47 +08:00
// CHECK-NEXT: "qualType": "__va_list_tag[1]"
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: "size": 1,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "RecordType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "__va_list_tag"
Print information about various type nodes when dumping the AST to JSON. llvm-svn: 364043
2019-06-21 21:22:35 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "decl": {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "name": "__va_list_tag"
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "file": "{{.*}}",
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 4,
// CHECK-NEXT: "col": 6,
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 3,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 4,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 3,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 4,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "a",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (Ty)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Ty"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 7,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 6,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 7,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 6,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 23,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 23,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0,
// CHECK-NEXT: "isParameterPack": true
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 7,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "b",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (Ty...)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Ty..."
// CHECK-NEXT: },
// CHECK-NEXT: "isParameterPack": true
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 10,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 9,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 10,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 9,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 30,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 21,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 30,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Uy",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 1
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 10,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "c",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (Ty)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Ty"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "name": "c",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (float)"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 13,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 12,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 13,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 25,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "previousDecl": "0x{{.*}}",
// CHECK-NEXT: "name": "c",
Include the mangled name in -ast-dump=json I am planning to use this feature to make update_cc_test_checks.py less fragile by obtaining the mangled names directly from -ast-dump=json. Currently, it uses c-index-test which ignores the -triple=, etc. arguments that are in the RUN: line and therefore does not generate checks for some targets. The AST dump tests were updated using the following command: `python $LLVM_BINDIR/gen_ast_dump_json_test.py --update --source $LLVM_SRC/clang/test/AST/*-json.*` Reviewers: aaron.ballman Reviewed By: aaron.ballman Subscribers: rsmith, MaskRay, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D69564
2019-11-15 20:33:16 +08:00
// CHECK-NEXT: "mangledName": "_Z1cIfiEvT_",
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (float)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "float"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "float"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 25,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "float"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 16,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 15,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 16,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "d",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 15,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTemplateParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 52,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 24,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 52,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Uy",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 1,
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
[clang] Make handling of unnamed template params similar to function params Summary: Clang uses the location identifier should be inserted for declarator decls when a decl is unnamed. But for type template and template template paramaters it uses the location of "typename/class" keyword, which makes it hard for tooling to insert/change parameter names. This change tries to unify these two cases by making template parameter parsing and sourcerange operations similar to function params/declarator decls. Reviewers: ilya-biryukov Subscribers: arphaman, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D68143 llvm-svn: 373340
2019-10-01 22:08:51 +08:00
// CHECK-NEXT: "col": 41,
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 33,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 1,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 16,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "d",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (Ty, Uy<Ty>)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Ty"
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
[clang] Implement ElaboratedType sugaring for types written bare Without this patch, clang will not wrap in an ElaboratedType node types written without a keyword and nested name qualifier, which goes against the intent that we should produce an AST which retains enough details to recover how things are written. The lack of this sugar is incompatible with the intent of the type printer default policy, which is to print types as written, but to fall back and print them fully qualified when they are desugared. An ElaboratedTypeLoc without keyword / NNS uses no storage by itself, but still requires pointer alignment due to pre-existing bug in the TypeLoc buffer handling. --- Troubleshooting list to deal with any breakage seen with this patch: 1) The most likely effect one would see by this patch is a change in how a type is printed. The type printer will, by design and default, print types as written. There are customization options there, but not that many, and they mainly apply to how to print a type that we somehow failed to track how it was written. This patch fixes a problem where we failed to distinguish between a type that was written without any elaborated-type qualifiers, such as a 'struct'/'class' tags and name spacifiers such as 'std::', and one that has been stripped of any 'metadata' that identifies such, the so called canonical types. Example: ``` namespace foo { struct A {}; A a; }; ``` If one were to print the type of `foo::a`, prior to this patch, this would result in `foo::A`. This is how the type printer would have, by default, printed the canonical type of A as well. As soon as you add any name qualifiers to A, the type printer would suddenly start accurately printing the type as written. This patch will make it print it accurately even when written without qualifiers, so we will just print `A` for the initial example, as the user did not really write that `foo::` namespace qualifier. 2) This patch could expose a bug in some AST matcher. Matching types is harder to get right when there is sugar involved. For example, if you want to match a type against being a pointer to some type A, then you have to account for getting a type that is sugar for a pointer to A, or being a pointer to sugar to A, or both! Usually you would get the second part wrong, and this would work for a very simple test where you don't use any name qualifiers, but you would discover is broken when you do. The usual fix is to either use the matcher which strips sugar, which is annoying to use as for example if you match an N level pointer, you have to put N+1 such matchers in there, beginning to end and between all those levels. But in a lot of cases, if the property you want to match is present in the canonical type, it's easier and faster to just match on that... This goes with what is said in 1), if you want to match against the name of a type, and you want the name string to be something stable, perhaps matching on the name of the canonical type is the better choice. 3) This patch could expose a bug in how you get the source range of some TypeLoc. For some reason, a lot of code is using getLocalSourceRange(), which only looks at the given TypeLoc node. This patch introduces a new, and more common TypeLoc node which contains no source locations on itself. This is not an inovation here, and some other, more rare TypeLoc nodes could also have this property, but if you use getLocalSourceRange on them, it's not going to return any valid locations, because it doesn't have any. The right fix here is to always use getSourceRange() or getBeginLoc/getEndLoc which will dive into the inner TypeLoc to get the source range if it doesn't find it on the top level one. You can use getLocalSourceRange if you are really into micro-optimizations and you have some outside knowledge that the TypeLocs you are dealing with will always include some source location. 4) Exposed a bug somewhere in the use of the normal clang type class API, where you have some type, you want to see if that type is some particular kind, you try a `dyn_cast` such as `dyn_cast<TypedefType>` and that fails because now you have an ElaboratedType which has a TypeDefType inside of it, which is what you wanted to match. Again, like 2), this would usually have been tested poorly with some simple tests with no qualifications, and would have been broken had there been any other kind of type sugar, be it an ElaboratedType or a TemplateSpecializationType or a SubstTemplateParmType. The usual fix here is to use `getAs` instead of `dyn_cast`, which will look deeper into the type. Or use `getAsAdjusted` when dealing with TypeLocs. For some reason the API is inconsistent there and on TypeLocs getAs behaves like a dyn_cast. 5) It could be a bug in this patch perhaps. Let me know if you need any help! Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Differential Revision: https://reviews.llvm.org/D112374
2021-10-12 00:15:36 +08:00
// CHECK-NEXT: "desugaredQualType": "Uy<Ty>",
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "qualType": "Uy<Ty>"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 19,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 18,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 19,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "e",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 18,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 19,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "e",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (Ty)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Ty"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 22,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 21,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 22,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "NonTypeTemplateParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 21,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 15,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 15,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "N",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: },
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 22,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (int)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 12,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: },
// CHECK-NEXT: "init": "c",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "DeclRefExpr",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: },
[clang] NFC: Rename rvalue to prvalue This renames the expression value categories from rvalue to prvalue, keeping nomenclature consistent with C++11 onwards. C++ has the most complicated taxonomy here, and every other language only uses a subset of it, so it's less confusing to use the C++ names consistently, and mentally remap to the C names when working on that context (prvalue -> rvalue, no xvalues, etc). Renames: * VK_RValue -> VK_PRValue * Expr::isRValue -> Expr::isPRValue * SK_QualificationConversionRValue -> SK_QualificationConversionPRValue * JSON AST Dumper Expression nodes value category: "rvalue" -> "prvalue" Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D103720
2021-06-05 05:15:23 +08:00
// CHECK-NEXT: "valueCategory": "prvalue",
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "referencedDecl": {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "NonTypeTemplateParmDecl",
// CHECK-NEXT: "name": "N",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 25,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 24,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 25,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "g",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 24,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 25,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 3
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0,
// CHECK-NEXT: "defaultArg": {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 25,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "g",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void (Ty)"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ParmVarDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "Ty"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 28,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 27,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 28,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "h",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 27,
[clang] Make handling of unnamed template params similar to function params Summary: Clang uses the location identifier should be inserted for declarator decls when a decl is unnamed. But for type template and template template paramaters it uses the location of "typename/class" keyword, which makes it hard for tooling to insert/change parameter names. This change tries to unify these two cases by making template parameter parsing and sourcerange operations similar to function params/declarator decls. Reviewers: ilya-biryukov Subscribers: arphaman, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D68143 llvm-svn: 373340
2019-10-01 22:08:51 +08:00
// CHECK-NEXT: "col": 20,
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 22,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0,
// CHECK-NEXT: "defaultArg": {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void"
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 28,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 6,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "h",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 31,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 30,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 31,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "R",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 30,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 31,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "R",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "R",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateSpecializationDecl",
// CHECK-NEXT: "name": "R"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateSpecializationDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 34,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 33,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 34,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 16,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "R",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "canPassInRegisters": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "R",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 37,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 36,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 37,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "S",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 36,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 30,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 24,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 5
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 30,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Uy",
// CHECK-NEXT: "tagUsed": "class",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 1
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 37,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "S",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "S",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplatePartialSpecializationDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 40,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 39,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 40,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "S",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "type-parameter-0-0"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "type-parameter-0-0"
// CHECK-NEXT: },
// CHECK-NEXT: "isDependent": true,
// CHECK-NEXT: "isInstantiationDependent": true,
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0,
// CHECK-NEXT: "decl": {
// CHECK-NEXT: "id": "0x0"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
AST dump: recurse into type template arguments when dumping. Also, do not dump the desugared type for a TemplateSpecializationType twice.
2020-06-23 15:01:38 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "BuiltinType",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "int"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 39,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isReferenced": true,
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 40,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "S",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 43,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 42,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 43,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "T",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "NonTypeTemplateParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 42,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 15,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "auto"
// CHECK-NEXT: },
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 43,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "T",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "T",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 46,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 45,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 46,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "U",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "NonTypeTemplateParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 45,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 25,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Reland (2) "[AST] Add RParen loc for decltype AutoTypeloc."" The patch was reverted because it caused a crash during PCH build -- we missed to update the RParenLoc in TreeTransform<Derived>::TransformAutoType. This relands 55d96ac and 37ec65e with a test and fix.
2022-01-14 18:28:04 +08:00
// CHECK-NEXT: "col": 24,
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "decltype(auto)"
// CHECK-NEXT: },
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 46,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "U",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "U",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "ClassTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 49,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 48,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 52,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "V",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 48,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Ty",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 49,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 52,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "V",
// CHECK-NEXT: "tagUsed": "struct",
// CHECK-NEXT: "completeDefinition": true,
// CHECK-NEXT: "definitionData": {
// CHECK-NEXT: "canConstDefaultInit": true,
// CHECK-NEXT: "copyAssign": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
PR46209: properly determine whether a copy assignment operator is trivial. We previously took a shortcut by assuming that if a subobject had a trivial copy assignment operator (with a few side-conditions), we would always invoke it, and could avoid going through overload resolution. That turns out to not be correct in the presenve of ref-qualifiers (and also won't be the case for copy-assignments with requires-clauses either). Use the same logic for lazy declaration of copy-assignments that we use for all other special member functions. Previously committed as c57f8a3a20540fcf9fbf98c0a73f381ec32fce2a. This now also includes an extension of LLDB's workaround for handling special members without the help of Sema to cover copy assignments.
2020-06-05 10:16:05 +08:00
// CHECK-NEXT: "simple": true,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "copyCtor": {
// CHECK-NEXT: "hasConstParam": true,
// CHECK-NEXT: "implicitHasConstParam": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "defaultCtor": {
// CHECK-NEXT: "defaultedIsConstexpr": true,
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "isConstexpr": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "dtor": {
// CHECK-NEXT: "irrelevant": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "hasConstexprNonCopyMoveConstructor": true,
// CHECK-NEXT: "isAggregate": true,
// CHECK-NEXT: "isEmpty": true,
// CHECK-NEXT: "isLiteral": true,
// CHECK-NEXT: "isPOD": true,
// CHECK-NEXT: "isStandardLayout": true,
// CHECK-NEXT: "isTrivial": true,
// CHECK-NEXT: "isTriviallyCopyable": true,
// CHECK-NEXT: "moveAssign": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: },
// CHECK-NEXT: "moveCtor": {
// CHECK-NEXT: "exists": true,
// CHECK-NEXT: "needsImplicit": true,
// CHECK-NEXT: "simple": true,
// CHECK-NEXT: "trivial": true
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXRecordDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 49,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 6
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "isImplicit": true,
// CHECK-NEXT: "name": "V",
// CHECK-NEXT: "tagUsed": "struct"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 51,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 50,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 51,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 50,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 22,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 22,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Uy",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 1,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 51,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 8,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 3,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 4
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 10,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "f",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 56,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 55,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 56,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
Generate parent context id from Decl* instead of DeclContext*. Because of multiple inheritance, a DeclContext pointer does not produce the same pointer representation as a Decl pointer that references the same AST Node. When dumping the parentDeclContextId field of a node, convert the pointer to Decl* first, so the id can be used to find the AST node it references. Patch by Bert Belder. llvm-svn: 370970
2019-09-05 04:30:00 +08:00
// CHECK-NEXT: "parentDeclContextId": "0x{{.*}}",
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "previousDecl": "0x{{.*}}",
// CHECK-NEXT: "name": "f",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 55,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 11,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 20,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 2
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "Uy",
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 1,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CXXMethodDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 56,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 13,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 54,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 1,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 8
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "line": 56,
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: },
Generate parent context id from Decl* instead of DeclContext*. Because of multiple inheritance, a DeclContext pointer does not produce the same pointer representation as a Decl pointer that references the same AST Node. When dumping the parentDeclContextId field of a node, convert the pointer to Decl* first, so the id can be used to find the AST node it references. Patch by Bert Belder. llvm-svn: 370970
2019-09-05 04:30:00 +08:00
// CHECK-NEXT: "parentDeclContextId": "0x{{.*}}",
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "previousDecl": "0x{{.*}}",
// CHECK-NEXT: "name": "f",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "CompoundStmt",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 17,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: "col": 18,
Augment location information when dumping the AST to JSON. Rather than create JSON objects for source locations and ranges, we instead stream them out directly. This allows us to elide duplicate information (without JSON field reordering causing an issue) like file names and line numbers, similar to the text dump. This also adds token length information when dumping the source location. llvm-svn: 364226
2019-06-25 04:07:11 +08:00
// CHECK-NEXT: "tokLen": 1
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }
// CHECK-NEXT: ]
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionTemplateDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "line": 59,
// CHECK-NEXT: "col": 6,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "line": 58,
// CHECK-NEXT: "col": 1,
// CHECK-NEXT: "tokLen": 8
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "line": 59,
// CHECK-NEXT: "col": 8,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTemplateParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "line": 58,
// CHECK-NEXT: "col": 37,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 11,
// CHECK-NEXT: "tokLen": 8
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 39,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "depth": 0,
// CHECK-NEXT: "index": 0,
// CHECK-NEXT: "defaultArg": {
// CHECK-NEXT: "kind": "TemplateArgument"
// CHECK-NEXT: },
// CHECK-NEXT: "inner": [
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "TemplateTypeParmDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 29,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 21,
// CHECK-NEXT: "tokLen": 8
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 21,
// CHECK-NEXT: "tokLen": 8
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "tagUsed": "typename",
// CHECK-NEXT: "depth": 1,
// CHECK-NEXT: "index": 0
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "kind": "TemplateArgument",
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 39,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 39,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-NEXT: "id": "0x{{.*}}",
// CHECK-NEXT: "kind": "FunctionDecl",
// CHECK-NEXT: "loc": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "line": 59,
// CHECK-NEXT: "col": 6,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: },
// CHECK-NEXT: "range": {
// CHECK-NEXT: "begin": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 1,
// CHECK-NEXT: "tokLen": 4
// CHECK-NEXT: },
// CHECK-NEXT: "end": {
[NFC] Make file offsets a regex to handle CRLF None of these tests are really intended to test the file offset as much as to test the structure. Making the regex allows this test to work even if the file is checked out with CRLF line endings. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D119362
2022-01-20 07:55:20 +08:00
// CHECK-NEXT: "offset": {{[0-9]+}},
Fix null ptr crash dumping TemplateTemplateParmDecl The following program winds up with D->getDefaultArgStorage().getInheritedFrom() == nullptr during dumping the TemplateTemplateParmDecl corresponding to the template parameter of i. template <typename> struct R; template <template <typename> class = R> void i(); This patch fixes the null pointer dereference.
2021-04-25 00:26:33 +08:00
// CHECK-NEXT: "col": 8,
// CHECK-NEXT: "tokLen": 1
// CHECK-NEXT: }
// CHECK-NEXT: },
// CHECK-NEXT: "name": "i",
// CHECK-NEXT: "type": {
// CHECK-NEXT: "qualType": "void ()"
// CHECK-NEXT: }
// CHECK-NEXT: }
// CHECK-NEXT: ]
Change the way we output templates for JSON AST dumping and dump information about template arguments. Previously, we attempted to write out template parameters and specializations to their own array, but due to the architecture of the ASTNodeTraverser, this meant that other nodes were not being written out. This now follows the same behavior as the regular AST dumper and puts all the (correct) information into the "inner" array. When we correct the AST node traverser itself, we can revisit splitting this information into separate arrays again. llvm-svn: 363819
2019-06-19 23:24:06 +08:00
// CHECK-NEXT: }
// CHECK-NEXT: ]
// CHECK-NEXT: }