Add build trace functions for MLE eval component

[andrewmilson]

This change is 

[andrewmilson]

• Create blake example that uses GKR for lookups #807
• Create MLE eval verifier component #805
• Create MLE eval prover component #804
• Add build trace functions for MLE eval component #803 👈
• Remove InteractionElements and LookupValues #802
• Pass entire mask to components #801
• Add MleCollection for accumulating MLEs #800
• Combine eq step constraints into single constraint #799
• Move all MLE eval related constraints into same module #798
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @andrewmilson and the rest of your teammates on Graphite

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.76%. Comparing base (8102837) to head (1e9e342).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #803   +/-   ##
=======================================
  Coverage   92.76%   92.76%           
=======================================
  Files          89       89           
  Lines       12032    12032           
  Branches    12032    12032           
=======================================
  Hits        11162    11162           
  Misses        763      763           
  Partials      107      107           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[spapinistarkware]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @andrewmilson and @shaharsamocha7)

---

crates/prover/src/examples/xor/gkr_lookups/mle_eval.rs line 156 at r1 (raw file):

    #[cfg(test)]
    assert_eq!(claim, mle.eval_at_point(eval_point));

Consider

Suggestion:

    debug_assert_eq!(claim, mle.eval_at_point(eval_point));

---

crates/prover/src/examples/xor/gkr_lookups/mle_eval.rs line 159 at r1 (raw file):

    let shift = claim / BaseField::from(mle.len());
    let packed_shift_coords = PackedSecureField::broadcast(shift).into_packed_m31s();
    let mut shifted_mle_terms_cols = mle_terms_cols.clone();

Suggestion:

let mut shifted_mle_terms_cols = mle_terms_cols;

---

crates/prover/src/examples/xor/gkr_lookups/mle_eval.rs line 188 at r1 (raw file):

) -> Vec<CircleEvaluation<SimdBackend, BaseField, BitReversedOrder>> {
    let log_size = N_VARIABLES as u32;
    vec![gen_is_first(log_size)]

Techinically, you can also compute this using vanishing cosets, same way you did for the smaller ones.

[andrewmilson]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @shaharsamocha7 and @spapinistarkware)

---

crates/prover/src/examples/xor/gkr_lookups/mle_eval.rs line 156 at r1 (raw file):

Previously, spapinistarkware (Shahar Papini) wrote…

Consider

need the cfg(test) since eval_at_point defined behind cfg(test)

---

crates/prover/src/examples/xor/gkr_lookups/mle_eval.rs line 159 at r1 (raw file):

    let shift = claim / BaseField::from(mle.len());
    let packed_shift_coords = PackedSecureField::broadcast(shift).into_packed_m31s();
    let mut shifted_mle_terms_cols = mle_terms_cols.clone();

ty

---

crates/prover/src/examples/xor/gkr_lookups/mle_eval.rs line 188 at r1 (raw file):

Previously, spapinistarkware (Shahar Papini) wrote…

Techinically, you can also compute this using vanishing cosets, same way you did for the smaller ones.

Done.

[spapinistarkware]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @shaharsamocha7)