chore!: limit pointer width in both crates

[dorimedini-starkware]

This change is 

[dorimedini-starkware]

Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion (waiting on @giladchase)

a discussion (no related file):
For this

---

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0af8a3e) 69.88% compared to head (e6384ef) 69.88%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1527   +/-   ##
=======================================
  Coverage   69.88%   69.88%           
=======================================
  Files          59       59           
  Lines        8180     8180           
  Branches     8180     8180           
=======================================
  Hits         5717     5717           
  Misses       2005     2005           
  Partials      458      458           

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

[elintul]

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @dorimedini-starkware and @giladchase)

a discussion (no related file):
Can you explain more?
What pointer are we limiting? What does the code you added mean?

---

[dorimedini-starkware]

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @elintul and @giladchase)

a discussion (no related file):

Previously, elintul (Elin) wrote…

Can you explain more?
What pointer are we limiting? What does the code you added mean?

Basically I am trying to limit usize to at most 128 bits (although index range is not the same as pointer length, it doesn't look like there will be a difference anytime soon).
The code I added means that the blockifier and native_blockifier libraries will be empty (no lib.rs) unless the architecture on which the code is compiled has pointer size in {16, 32, 64,128}.

---

[elintul]

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @dorimedini-starkware and @giladchase)

a discussion (no related file):

Previously, dorimedini-starkware wrote…

Basically I am trying to limit usize to at most 128 bits (although index range is not the same as pointer length, it doesn't look like there will be a difference anytime soon).
The code I added means that the blockifier and native_blockifier libraries will be empty (no lib.rs) unless the architecture on which the code is compiled has pointer size in {16, 32, 64,128}.

Please document this for future readers.

---

[dorimedini-starkware]

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @elintul and @giladchase)

a discussion (no related file):

Previously, elintul (Elin) wrote…

Please document this for future readers.

Done.

---

[elintul]

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