On 01/29/2013 10:26 PM, Walter Bright wrote:
valgrind is immensely useful for C, but a lot less so for D as D guarantees initialization and a GC takes care of much of the rest.
On the subject of valgrind and D's garbage collection -- when I've run any D program through valgrind's memory check, it always reports a small amount of memory that has failed to deallocate at the end of the program (IIRC it's about 3 allocs that valgrind thinks have not been deallocated).
Is there any particular reason why this should be so? Is it an error in D or in valgrind's tracking of D's memory management?
