Storage slot 0 is unusable

[LHerskind]

Using storage slot 0 in your noir contract will make the storage non-updatable, e.g., writes wont take effect, it will just be a returning value 0 every time it is read afterwards.

This should either be allowed, or it should throw an error at compile time to make sure the contracts don't to this.

[iAmMichaelConnor]

We probably can't catch it at compile time, yet, but we could catch it at runtime within each state variable constructor (or within a helper function which is called by each state variable constructor).

Tagging @sirasistant @LeilaWang , as there's some work being done to give nice runtime errors. This might be useful for this issue as well assert(storage_slot != 0, "Storage slot 0 not allowed. Storage slots must start from 1.");

It's a shame Noir can't do compile-time assertions, like barretenberg can :P

[sirasistant]

If there is an assertion with all the values constant, I think it will be caught at compile time! So we can introduce this slot assertion in our libs

[sirasistant]

And the devex will be even better with assert messages