🚀 go-pugleaf

You are confusing documentation of a particular implementation with a spec.

From some equally SystemV-ish man-pages (for libmalloc):

	  The argument to free is a pointer to a block previously
	  allocated by malloc; after free is performed this space is
	  made available for further allocation, and its contents have
	  been destroyed (but see mallopt below	for a way to change
	  this behavior).

In fact I was using neither of these implementations when I ran into the
problem, but that doesn't matter because the closedir() code should have been
written with the spec in mind, not the (documented) behaviour of a particular
implementation.

Lets not turn this into comp.lang.c.