thunk: clear thunk instance payloads

Since thunk instances are utilized via initializer functions
which always initialize all the environment members, it made
sense to use plain malloc().

But with the addition of payloads, there's a component of the
allocation which gets split out for the caller to make use of
in a much more ad-hoc fashion.

In my personal programming style, I tend to take advantage of the
assumption that allocations are zeroed.  The returned payload is
essentially used as a heap allocation, just coupled to the thunk
instance in terms of life cycle.  So I prefer the payload space
be zeroed on allocation.

Since it still seems sensible to leave the thunk's environment
part of the instance exclusively initialized by it's init
function, this commit leaves the plain malloc and just memset's
the payload when present.

0 files changed, 0 insertions, 0 deletions