Skip to content

Various software engineering correctness tools #20

Description

@rhaps0dy

Here's a list of things we might do to reduce PR bickering and improve software correctness. I think they're not worth it now (except black and maybe basic CI) but here's a list anyways:

  • Automatic formatting

    • Python (black)
    • C++ (clang-format)
  • Coverage reports

    • Especially: compare coverage reports in tests vs. experiments. If significant parts of the experiment coverage aren't covered by tests, we're in trouble
  • Continuous integration: Automatically run tests before merging every PR

  • Build with clang (faster, more warnings, as a downside IDK if valgrind works)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions