catch3/src/catch2/internal/catch_xmlwriter.hpp, branch v3.0.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Rename catch_stream -> catch_reusable_string_stream 2022-04-16T14:34:08+00:00 Martin Hořeňovský 2022-04-16T13:00:41+00:00 7b93a2014cb417d277339e3d679cac64bfac237b After everything else was split out, this name much reflects the actual contents of the file(s). 
After everything else was split out, this name much reflects the
actual contents of the file(s).
Some IWYU include cleanups 2022-04-14T15:16:01+00:00 Martin Hořeňovský 2022-04-14T15:16:01+00:00 c742ea9ad97a34c8f652dd7f67012d5b3f818c2d 






Remove pointless mutable from ScopedElement's XmlWriter ptr
2022-04-12T20:31:51+00:00

Martin Hořeňovský

2022-04-12T20:31:47+00:00

9934b7de13ef303e0d7b1bccf519422be73c6a03












Remove superfluous default argument from XMLWriter's constructor
2022-04-12T20:28:40+00:00

Martin Hořeňovský

2022-04-12T20:28:36+00:00

7a89916198743dafce72854f97b88a659c0d875b












Remove XmlWriter::writeBlankLine
2021-10-02T12:39:54+00:00

Martin Hořeňovský

2021-10-02T09:45:19+00:00

3e9c6fec222a5b307a712ba47dc4e930b37ad4e5

There is no good reason to provide a "add empty line" primitive
for writing XML documents, and the fact that it remains unused
after all the time it was provided only confirms this further.





There is no good reason to provide a "add empty line" primitive
for writing XML documents, and the fact that it remains unused
after all the time it was provided only confirms this further.







Add more tests for XmlWrite::write* members
2021-10-02T12:39:52+00:00

Martin Hořeňovský

2021-10-01T10:02:17+00:00

13670f535fad8ab5db06049366a38f7a364d37d8












Improve XmlWriter::writeAttribute overload set for string-like types
2021-05-30T11:06:03+00:00

Martin Hořeňovský

2021-05-30T11:05:07+00:00

41ad0fda11d0898ce3aaeee9db4e7bc16eec5051

Previously, string literals and `std::string`s would match the
template variant, which would serialize them into a stream and then
call the `StringRef` overload for resulting string. This caused
bunch of codebloat and unnecessary pessimization for common usage.





Previously, string literals and `std::string`s would match the
template variant, which would serialize them into a stream and then
call the `StringRef` overload for resulting string. This caused
bunch of codebloat and unnecessary pessimization for common usage.







Use StringRef instead of std::string in XmlWriter::ScopedElement
2021-05-29T19:47:12+00:00

Martin Hořeňovský

2021-05-29T19:35:18+00:00

d9f72868b2662c505bad3f5d47163816573bc14a












Use StringRef in XmLWriter when the text is not stored
2021-05-29T19:23:24+00:00

Martin Hořeňovský

2021-05-29T16:38:07+00:00

c7241bb76e383e103792b47119ae5e742120e7f4












Use StringRef through XmlEncode
2021-05-29T14:41:57+00:00

Martin Hořeňovský

2021-05-29T14:37:51+00:00

1d04427fcdf81fb13c754c659f4bcde0403a8855

This introduces a potential lifetime risk when using the API, but
the intended way to use the `XmlEncode` class is to use it directly,
e.g. `out << XmlEncode(some-text-argument)`, not to store it around.

The benefit is that we avoid allocations for strings that do not fit
into SSO for given platform.





This introduces a potential lifetime risk when using the API, but
the intended way to use the `XmlEncode` class is to use it directly,
e.g. `out << XmlEncode(some-text-argument)`, not to store it around.

The benefit is that we avoid allocations for strings that do not fit
into SSO for given platform.