[Pickles] Avoid recomputation of cached verification keys #14412
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes what
Pickles.Cache
returns inread_or_generate
, from a keypair (prover and verifier key,Impl.Keypair.t
) to a prover key (Impl.Prover_key.t
, which is just a Rust prover index).The verifier key on the
Keypair.t
structure was never used, but still expensively recomputed when reading prover keys from cache.