catchorg / catchorg/Catch2

Stringification of big ranges

Open
#2,358 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
21.5k
Forks
3.5k
Avg merge
3d 16h
Merged PRs (30d)
2

Description

I happen to have a `CHECK(buffer1 == expectedbuffer)`, with each buffers being whopping a 5MB.

When you use the `-s` switch, catch2 is happy to print all of it, really really slowly.

**Expected behavior**
I would have expect the stringification of ranges to have some kind of limit. Both for performance and readability reason.

**workaround**

* Specialize StringMaker to do it, but this cumbersome, particularly with ODR.

* Use a hashed value of the buffer in the `CHECK` expression. Not pratical when you have lots of them.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.