mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-06-26 21:20:30 +02:00
f1b660484e
Whether the returned object needs to be cleared or not depends on a couple things: - Whether the embedder actually needs the object to be cleared. - Whether the collector allocated the object from memory that was all zeroes already. The goal of course would be to prevent clearing memory if the mutator was just going to write all over it. But it's hard to know statically if the memory would have been all zeroes anyway, and in that case if you did clear it you'd be doing double work. In the end it's simpler to just require collectors to clear memory in bulk. We can revisit this later if it is an issue. |
||
|---|---|---|
| .. | ||
| bdw-attrs.h | ||
| gc-api.h | ||
| gc-assert.h | ||
| gc-attrs.h | ||
| gc-basic-stats.h | ||
| gc-collection-kind.h | ||
| gc-config.h | ||
| gc-conservative-ref.h | ||
| gc-edge.h | ||
| gc-embedder-api.h | ||
| gc-ephemeron.h | ||
| gc-event-listener-chain.h | ||
| gc-event-listener.h | ||
| gc-finalizer.h | ||
| gc-forwarding.h | ||
| gc-histogram.h | ||
| gc-inline.h | ||
| gc-lttng.h | ||
| gc-null-event-listener.h | ||
| gc-options.h | ||
| gc-ref.h | ||
| gc-tracepoint.h | ||
| gc-visibility.h | ||
| mmc-attrs.h | ||
| pcc-attrs.h | ||
| semi-attrs.h | ||