llvm-project.git/llvm/unittests/Support/YAMLParserTest.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [YAMLParser] Unfold multi-line scalar values (#70898) 2023-11-10T00:19:24+00:00 Igor Kudrin ikudrin@accesssoftek.com 2023-11-10T00:19:24+00:00 652ceaddc0ea899f4d3edef66715ae164e3d8c4d Long scalar values can be split into multiple lines to improve readability. The rules are described in Section 6.5. "Line Folding", https://yaml.org/spec/1.2.2/#65-line-folding. In addition, for flow scalar styles, the Spec states that "All leading and trailing white space characters on each line are excluded from the content", https://yaml.org/spec/1.2.2/#73-flow-scalar-styles. The patch implements these unfolding rules for double-quoted, single-quoted, and plain scalars. 
Long scalar values can be split into multiple lines to improve
readability. The rules are described in Section 6.5. "Line Folding",
https://yaml.org/spec/1.2.2/#65-line-folding. In addition, for flow
scalar styles, the Spec states that "All leading and trailing white
space characters on each line are excluded from the content",
https://yaml.org/spec/1.2.2/#73-flow-scalar-styles.

The patch implements these unfolding rules for double-quoted,
single-quoted, and plain scalars.
 [YAMLParser] Improve plain scalar spec compliance (#68946) 2023-10-17T17:28:14+00:00 akirchhoff-modular 29713761+akirchhoff-modular@users.noreply.github.com 2023-10-17T17:28:14+00:00 4480e650b3cf7cc63cfd3767cd6b120f8bfad2ac The `YAMLParser.h` header file claims support for YAML 1.2 with a few deviations, but our plain scalar parsing failed to parse some valid YAML according to the spec. This change puts us more in compliance with the YAML spec, now letting us parse plain scalars containing additional special characters in cases where they are not ambiguous. 
The `YAMLParser.h` header file claims support for YAML 1.2 with a few
deviations, but our plain scalar parsing failed to parse some valid YAML
according to the spec. This change puts us more in compliance with the
YAML spec, now letting us parse plain scalars containing additional
special characters in cases where they are not ambiguous.
 YAMLParser: llvm::Optional => std::optional 2022-12-15T09:34:31+00:00 Fangrui Song i@maskray.me 2022-12-15T09:34:31+00:00 8b61376dfa1d67ef2776bcb4a5f92095132ce2fa 






[llvm] Use has_value instead of hasValue (NFC)
2022-07-13T05:25:42+00:00

Kazu Hirata
kazu@google.com

2022-07-13T05:25:42+00:00

3361a364e64c815ede2fe6dfe4e8016637c16b0b












Revert "Don't use Optional::hasValue (NFC)"
2022-06-25T18:56:50+00:00

Kazu Hirata
kazu@google.com

2022-06-25T18:56:50+00:00

3b7c3a654c9175f41ac871a937cbcae73dfb3c5d

This reverts commit aa8feeefd3ac6c78ee8f67bf033976fc7d68bc6d.





This reverts commit aa8feeefd3ac6c78ee8f67bf033976fc7d68bc6d.







Don't use Optional::hasValue (NFC)
2022-06-25T18:55:57+00:00

Kazu Hirata
kazu@google.com

2022-06-25T18:55:57+00:00

aa8feeefd3ac6c78ee8f67bf033976fc7d68bc6d












[NFCI][Support] Avoid ASSERT_/EXPECT_TRUE(A <op> B)
2022-01-21T13:15:04+00:00

Archibald Elliott
archibald.elliott@arm.com

2022-01-21T13:14:58+00:00

38ac4093d9d2ae28d631ca1cc5802533989165c5

The error messages in tests are far better when a test fails if the test
is written using ASSERT_/EXPECT_<operator>(A, B) rather than
ASSERT_/EXPECT_TRUE(A <operator> B).

This commit updates all of llvm/unittests/Support to use these macros
where possible.

This change has not been possible in:
- llvm/unittests/Support/FSUniqueIDTest.cpp - due to not overloading
  operators beyond ==, != and <.
- llvm/unittests/Support/BranchProbabilityTest.cpp - where the unchanged
  tests are of the operator overloads themselves.

There are other possibilities of this conversion not being valid, which
have not applied in these tests, as they do not use NULL (they use
nullptr), and they do not use const char* (they use std::string or
StringRef).

Reviewed By: mubashar_

Differential Revision: https://reviews.llvm.org/D117319





The error messages in tests are far better when a test fails if the test
is written using ASSERT_/EXPECT_<operator>(A, B) rather than
ASSERT_/EXPECT_TRUE(A <operator> B).

This commit updates all of llvm/unittests/Support to use these macros
where possible.

This change has not been possible in:
- llvm/unittests/Support/FSUniqueIDTest.cpp - due to not overloading
  operators beyond ==, != and <.
- llvm/unittests/Support/BranchProbabilityTest.cpp - where the unchanged
  tests are of the operator overloads themselves.

There are other possibilities of this conversion not being valid, which
have not applied in these tests, as they do not use NULL (they use
nullptr), and they do not use const char* (they use std::string or
StringRef).

Reviewed By: mubashar_

Differential Revision: https://reviews.llvm.org/D117319







[YAML] Support extended spellings when parsing bools.
2020-12-12T12:50:34+00:00

Nathan James
n.james93@hotmail.co.uk

2020-12-12T12:50:33+00:00

0e5bfffb1361727eb163c4ecdd5836818064240f

Support all the spellings of boolean datatypes according to https://yaml.org/type/bool.html

Reviewed By: silvas

Differential Revision: https://reviews.llvm.org/D92755





Support all the spellings of boolean datatypes according to https://yaml.org/type/bool.html

Reviewed By: silvas

Differential Revision: https://reviews.llvm.org/D92755







Fix null dereference in yaml::Document::skip
2019-11-12T04:48:28+00:00

Thomas Finch
tfinch@apple.com

2019-11-12T04:48:28+00:00

ac385ca63fe8bc283d7f5be213319cc3b930b4cc

Summary: The attached test case replicates a null dereference crash in
`yaml::Document::skip()`. This was fixed by adding a check and early
return in the method.

Reviewers: Bigcheese, hintonda, beanz

Reviewed By: hintonda

Subscribers: hiraditya, dexonsmith, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D69974





Summary: The attached test case replicates a null dereference crash in
`yaml::Document::skip()`. This was fixed by adding a check and early
return in the method.

Reviewers: Bigcheese, hintonda, beanz

Reviewed By: hintonda

Subscribers: hiraditya, dexonsmith, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D69974







Update the file headers across all of the LLVM projects in the monorepo
2019-01-19T08:50:56+00:00

Chandler Carruth
chandlerc@gmail.com

2019-01-19T08:50:56+00:00

2946cd701067404b99c39fb29dc9c74bd7193eb3

to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

llvm-svn: 351636





to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

llvm-svn: 351636