Although informal timings put the cost at ~4us, it's hashing that is not needed. Much like the file entries themselves, the hash only need be checked on extraction, which, for lift manifests, is only when the scie.boot is involved (see #7).
Typical informal timings in a noop dispatch timer test rig of:
Aha, right. This is ~impossible. The lift manifest doesn't current have its size and hash stored. The size could be stored but not the hash - since the hash value would change the hash!
Currently, the lift manifest is digested on every run of a scie even if it already has a hash recorded: https://github.com/a-scie/jump/blob/12d714431e929457be315502485daaae4e3e68d2/jump/src/lift.rs#L173-L204
Although informal timings put the cost at ~4us, it's hashing that is not needed. Much like the file entries themselves, the hash only need be checked on extraction, which, for lift manifests, is only when the scie.boot is involved (see #7).
Typical informal timings in a noop dispatch timer test rig of: