Remove statements with not reliable libfunc

[ksew1]

Closes #

Introduced changes

• Remove statements with unreliable libfuncs. These are libfuncs that are meaningful only at the Sierra level (no cost at CASM) level, and sometimes the VM does not execute them.

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Performed self-review of the code
• Added changes to CHANGELOG.md

[piotmag769]

These are libfuncs that are meaningful only at the CASM level, and sometimes the VM does not execute them.

Wdym by that? Looking at the libfuncs you selected like drop, didn't you mean "meaningful only at Sierra level"?

[piotmag769]

One Sierra return should map to one CASM return, no? How is that libfunc not reliable?

[ksew1]

Correct me if I'm wrong, but it's because it has no cost. The libfunc that has no cost seems (sometimes?) not to be executed. It needs more investigation definitely in #98

[piotmag769]

It has a cost at CASM level https://docs.cairo-lang.org/how_cairo_works/functions.html#under-the-hood

[ksew1]

These are libfuncs that are meaningful only at the CASM level, and sometimes the VM does not execute them.

Wdym by that? Looking at the libfuncs you selected like drop, didn't you mean "meaningful only at Sierra level"?

Yep my bad. Should be "libfuncs that are meaningful only at the Sierra level (no cost at CASM)" corrected

[piotmag769]

and sometimes the VM does not execute them.

[nit] since they are Sierra libfuncs, VM doesn't execute them. You can say that they don't have a corresponding instruction at CASM lvl or sth