Replies: 2 comments 5 replies
-
|
I believe that leak detection and GTest integration are the only features that rely on "less-than-standard" language constructs. Both of these features are optional and can be disabled. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we've disabled them in an existing project, which is migrating to C++20.
|
Beta Was this translation helpful? Give feedback.
-
|
We run tests against C++20 builds with GCC, Clang, and MSVC. It should work fine. |
Beta Was this translation helpful? Give feedback.
-
|
@geipel I assume you are only talking about standard library support? The memory leak detection always clashed with standard library, so I would assume there are no changes required. Is that correct? |
Beta Was this translation helpful? Give feedback.
-
|
Well, I don't know. Given that there hasn't been a release in four years, I'm wondering if this is being actively maintained. |
Beta Was this translation helpful? Give feedback.
-
|
It is up to you. I'm at the moment the main maintainer and I don't have time for doing releases, especially as most people just use the trunk and there are not very major changes in recent years. We will expand the maintainers group in the future. I have no intention to completely stop maintaining it especially as it has an active usage community. |
Beta Was this translation helpful? Give feedback.
-
|
OK. I have not tried a version on the trunk, as we have only used released builds, historically. Thanks for your responses. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This library manipulates the STL to support features like memory leak detection.
It seems unlikely that this will work without changes for C++20.
The last release was over four years ago. Is there a plan for updated releases?
Beta Was this translation helpful? Give feedback.
All reactions