Optimise the source code as neatly as possible (see valgrind --leak-check=yes --track-origins=yes)
Better naming system for variables
Use the same coding style everywhere (make use of clang-format)
* Optimise the source code as neatly as possible (see `valgrind --leak-check=yes --track-origins=yes`)
* Better naming system for variables
* Use the same coding style everywhere (make use of `clang-format`)
_N0x
changed title from Optimise the sourcecode to have as little leaks as possible and free up memory [valgrin to Optimise the sourcecode to have as little leaks as possible and free up memory [valgring]2022-02-20 01:07:25 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
valgrind --leak-check=yes --track-origins=yes)clang-format)Optimise the sourcecode to have as little leaks as possible and free up memory [valgrinto Optimise the sourcecode to have as little leaks as possible and free up memory [valgring]A big focus should also be put on how to to free up cJSON data structures since those are causing almost all leaks currently within the code