Expand description
What data sits under each version, and what belongs to none of them.
Iterating five versions of one question in an afternoon leaves five sets of intermediates in the store, and a month later nobody can say which was whose. Nothing is written down to answer that: a probe already says what every node’s answer will be called, so attribution is two questions to the store and no index anybody has to keep up to date.
Two ways to attribute, kept both because they say different things. By key: a key that matches means this is exactly the value that version would ask for — exact, and fragile in one place, since a key is computed against the probing interpreter’s environment, so probing a three-month-old commit today gives keys that match nothing stored back then. By fingerprint: whoever ran wrote which node and which code version produced each value, so it answers about old data, which is what nobody can attribute from memory.
A value whose fingerprint belongs to no version nameable here comes out anyway, saying so. Keeping it quiet would let the mute hashes back in through the back door.
Structs§
- Belongs
- A value in the store, and which version it turned out to be from.
Enums§
- How
- How a value was found to belong to a version.
Constants§
- ENVIRONMENT
- What the environment a value was produced against is called in its
meta.
Functions§
- under
- What is in the store, attributed to the versions passed in.