Arkadiusz
> The name is bad, but in general I don't see why they couldn't be put into cairo-lang. Because it doesn't have to be in that package. Changes to `cairo-lang`...
I am not sure about renaming `src` to `contracts`. I noticed in a few projects this naming convention, e.g.: https://github.com/jediswaplabs/JediSwap. Also, some people keep contracts and frontend code in the...
Let's leave the `src` then.
Is this cheatcode really needed? A user should be able to test internal functions with "pure Cairo" test runner.
A user could use [impureim sandwich](https://blog.ploeh.dk/2020/03/02/impureim-sandwich/). Pure functions could be tested with pure Cairo and storage modifications could be tested with Cheatable Starknet fixture.
Protostar doesn't crash, so it's fixed to me. Loading constants.json in the unbuild version of Protostar requires a different logic.
Reference — Caching in Buck: https://youtu.be/uvNI_E0ZgZU?t=976
Scarb should be responsible for caching Cairo compilation results.
Contract name in tests should resolve to the build output. Caching would be a functionality of `protostar build`.
https://discord.com/channels/793094838509764618/964116575387021413/1050049462967484436