theoludwig/libcproject

[Improvement] Clean up memory leaks and memory allocations

theoludwig opened this issue ยท 1 comments

Proposal

Currently, we use sizeof(char*) and sizeof(char) interchangeably, we should make a diiference as they are not the same thing, and we should allocate as little memory as possible.

Screenshot from 2023-06-26 18-19-16

Also running the automated tests by compiling with the gcc flag -fsanitize=address, it yields a bunch of errors.

Could be a good practice to run valgrind to check for memory leaks.

YouTube - Jacob Sorber- find memory errors quickly. (-fsanitize, addresssanitizer)

๐ŸŽ‰ This issue has been resolved in version 3.0.0 ๐ŸŽ‰

The release is available on GitHub release

Your semantic-release bot ๐Ÿ“ฆ๐Ÿš€