Closed rodrigo-pino closed 1 year ago
Is there any behaviour test we could uncomment?
I wouldn't do it just yet. During memory development we found a bunch of small errors scattered everywhere we are currently solving. I think we should start testing behaviour with non memory/storage/calldata stuff first if possible, to also discard possible errors on the testnet side
Is there any behaviour test we could uncomment?
I wouldn't do it just yet. During memory development we found a bunch of small errors scattered everywhere we are currently solving. I think we should start testing behaviour with non memory/storage/calldata stuff first if possible, to also discard possible errors on the testnet side
We are already running behaviour tests that are non memory/storage/calldata
https://github.com/NethermindEth/warp/pull/1045#discussion_r1208123402
I've made a search for functions that start with "try_" in the Cairo codebase and in all cases it's functions that might return a failure (Option
), but not panic.
Since this function may panic, it might probably make sense to prefix it with "unsafe".
cc @piwonskp @rodrigo-pino
(for some reason, I can't reply in the thread itself)
Is there any behaviour test we could uncomment?