static_assert is all you need (no leaks, no UB)

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  1. TDD

    See while you code

    Keep tests and code separate, and use tdd: https://github.com/yellowdragonlabs/TDD

    I usually have dozens/hundreds of tests that run faster than you can compile #include .

    All tests are executed automatically every time I save. It's very nice to watch the output while coding, with almost no latency.

  2. InfluxDB

    InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

    InfluxDB logo
  3. templight

    Templight is a Clang-based tool to profile the time and memory consumption of template instantiations and to perform interactive debugging sessions to gain introspection into the template instantiation process.

    IMHO the best approach is to avoid the problem by applying TDD. Then there is very little need to debug anything. But otherwise, there is https://github.com/mikael-s-persson/templight for compile-time debugging which is pretty cool and having something like `expect(auto... args) static_asert(args...); assert(args...);` may help with being able to debug at run-time and get the coverage (though, the code has has to compile aka pass first).

  4. examc

    proof of concept C unit test library using linker sections

    There are other ways to do this. I made a proof of concept of using linker sections to allow you to sprinkle tests within the implementation inline once... https://github.com/cozzyd/examc (this is obviously not production-ready, just serves as a proof of concept).

    Basically the idea is that the test code gets written to a different linker section that your test runner can iterate through, when tests are enabled.

  5. samples

    You can now specify a directory, see README. Any other arguments are just passed to the compiler.

    Here's a sample to play with: https://github.com/yellowdragonlabs/samples/blob/master/tdd_...

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Introducing CI Pipeline for Clang-Format Checks in faker-cxx

    1 project | dev.to | 21 Nov 2024
  • Increasing Code Coverage in faker-cxx

    1 project | dev.to | 21 Nov 2024
  • Testing framework Catch2 3.0 final released

    3 projects | /r/cpp | 17 May 2022
  • Getting started with Boost in 2022

    5 projects | /r/cpp | 14 Apr 2022
  • C++17 python like print function

    4 projects | /r/embedded | 9 Mar 2022

Did you know that C++ is
the 7th most popular programming language
based on number of references?