Ark
Ark copied to clipboard
Write C++ the right way
Is your feature request related to a problem?
If you are developing blindly, without any tool guidance, you are doing C++ wrong. Think of these tools like a backup camera in your car. Certainly you can back up without a camera, but having one gives you a second set of eyes, deeper into the action than is possible with your human eyes. https://github.com/lefticus/cpp_weekly/issues/175
Describe the solution you would like
Implement as much as possible from this list: https://github.com/lefticus/cpp_weekly/issues/175
- [x] add CI
- [ ] setup tests (use something like approval tests if starting with existing code)
- related to:
- [x] #409
- [x] #410
- [x] #403
- [x] #328
- [ ] #260
- [ ] enable as many warnings as possible:
- [ ] #460
- [ ] turn on warnings as errors
- [x] add 2 (or more) compilers
- [ ] add static analysis tools
- [x] should run in the CI
- [ ] #461
- [ ] enable runtime analysis
- [x] valgrind
- [ ] sanitizers:
- [x] ASAN (#396)
- [ ] MSAN
- [x] UBSAN (#396)
- [ ] TSAN
- [x] fuzzing
- [x] enable fuzzing in the CI (#422)
- [x] #465
- [x] #467
Is it a big modification to the language? Leave it if you don't know
- [ ] Breaking change
- [ ] Compiler/syntax modifications
- [x] Runtime modifications (standard library, modules, packages...)