In practice, there is usually a ref count held on a header by a higher level
container like a ts or a mi.
In C it's usually quick to use valgrind, or compile with -fsanitize=address to
fix occasional mistakes. I don't know enough about rust tools used to check
memory problems at runtime, though it seems like there's a strong attempt to
prevent memory issues within the language itself.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Rpm-maint mailing list