catch3/include/internal/catch_stringref.h, branch v2.10.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Reinline some StringRef methods with trivial bodies 2019-09-08T19:08:37+00:00 Martin Hořeňovský 2019-09-08T19:08:37+00:00 a156440b19c1103419b6e4d3ebbfe3c7ddb948dc 






Remove (mostly) unused overloads of StringRef operator +
2019-09-08T19:01:33+00:00

Martin Hořeňovský

2019-09-08T19:01:33+00:00

9f4c4777a5136a3e1f276398799961e9ccb4b572












Make StringRef's operator std::string explicit
2019-09-08T13:58:10+00:00

Martin Hořeňovský

2019-09-08T12:49:40+00:00

7b865daccc7bba2dcc25a4f0b9ea7348b1b4d61f

This way it is explicit when there is a `StringRef` -> `std::string`
conversion and makes it easier to look for allocations that could
be avoided.

Doing this has already removed one allocation per registered test
case, as there was a completely pointless `StringRef` -> `std::string`
conversion when parsing tags of a test case.





This way it is explicit when there is a `StringRef` -> `std::string`
conversion and makes it easier to look for allocations that could
be avoided.

Doing this has already removed one allocation per registered test
case, as there was a completely pointless `StringRef` -> `std::string`
conversion when parsing tags of a test case.







Remove the ill-considered StringRef::numberOfCharacters
2019-09-07T18:13:22+00:00

Martin Hořeňovský

2019-09-07T18:13:22+00:00

fe967b1f4122a67ae1b31febf26cf1751917a0eb

It never counted characters, only codepoints. If you think these
are interchangeable, you should not touch non-ascii text.





It never counted characters, only codepoints. If you think these
are interchangeable, you should not touch non-ascii text.







Remove commented out code
2019-05-26T19:19:55+00:00

Martin Hořeňovský

2019-05-26T19:19:55+00:00

a5a2d08fbb3f68cf3f0bfbaa11e8b7a2d4386d61












StringRef no longer repoints m_start to m_data after c_str() on a substring.
2019-05-20T23:04:44+00:00

Phil Nash

2019-05-20T23:04:19+00:00

96355da34edf51cc813400115984050bd7c50630

This fixes an issue where a self-assignment of a StringRef copy would point into internally (and now dangling) data.
(now self-assignment check is no longer needed)





This fixes an issue where a self-assignment of a StringRef copy would point into internally (and now dangling) data.
(now self-assignment check is no longer needed)







Fix StringRef self-assignment after substring
2019-05-18T16:54:39+00:00

Phil Nash

2019-05-18T16:54:06+00:00

3bce8ba14b5dfb55c0127b8ad9eddf5a92b662c0

Thanks to Alex Tkachenko for spotting it.





Thanks to Alex Tkachenko for spotting it.







small cleanup of code
2019-01-10T12:07:54+00:00

Jozef Grajciar

2019-01-06T13:03:19+00:00

bdee512057fd896025bde6dcd2b837de522161a1












Introduce "C-namespaced" UDL for StringRef
2018-07-23T12:00:45+00:00

Martin Hořeňovský

2018-07-23T11:19:21+00:00

f7f592dfc96086ddaaf77150b072adbca4627dc8












Provide a public method to get StringRef's underlying pointer
2018-02-28T21:49:00+00:00

Martin Hořeňovský

2018-02-28T21:05:01+00:00

05cd05743a75caeffbd6ad4c675ac68bc8e270f1

This allows reducing the amount of friends needed for its interface
and some extra tricks later.

The bad part is that the pointer can become invalidated via
calls to other StringRef's public methods, but c'est la vie.





This allows reducing the amount of friends needed for its interface
and some extra tricks later.

The bad part is that the pointer can become invalidated via
calls to other StringRef's public methods, but c'est la vie.