Test memory trace.

[alonh5]

This change is 

[alonh5]

• Test memory trace. #27 👈
• Get range check inputs one by one. #25
• Implement memory component prover. #24
• Write memory interaction trace. #23
• Add memory component. #19
• Evaluate constraints together. #18
• Add lookup step constraint. #17
• Add last lookup boundary constraint. #16
• Implement ComponentProver for RangeCheckUnitComponent. #13
• Implement Component for RangeCheckUnitComponent. #12
• Update stwo and fix changes. #11
• Add rust format file. #14
• main

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

Join @alonh5 and the rest of your teammates on Graphite

[shaharsamocha7]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @alonh5)

---

stwo_cairo_prover/src/components/memory/component.rs line 256 at r1 (raw file):

            .write_interaction_trace(&trace.iter().collect(), &interaction_elements);

        let mut trace_sum = SecureField::zero();

rename

Suggestion:

expected_logup_sum

[alonh5]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @shaharsamocha7)

---

stwo_cairo_prover/src/components/memory/component.rs line 256 at r1 (raw file):

Previously, shaharsamocha7 wrote…

rename

Done.

[shaharsamocha7]

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