feat: add os.Exit

[albttx]

Description

Allow to exit a realm

[piux2]

Can you describe 1) the problem to solve and 2) the trade-off made with this solution?

We should put extra cautious in creating the native method in stdlibs to alter the state or intercept the execution of the machine.

[albttx]

In case you need to exit in a smart contract

[piux2]

In case you need to exit in a smart contract

Sure, in what cases do we need to exit a smart contract that can not be handled at the end of the function call in a package managed by GVM runtime?

Calling os.exit() directly from a contract breaks the contract call flow and GVM persistent flow.

[moul]

panic() informs users of what went wrong in the event of a failure. To allow for silent panicking, let's create a type that displays less intimidating stack traces through #416. While developers may prefer exiting gracefully, users want to know what happened if the contract fails, and panic() already satisfies this need. If we improve our panic() handling, I'm open to making so.Exit a panic(silentExit{}) shortcut.

[anarcher]

IMHO, Inside a VM, it seems like a good idea to define an operation like op.Exit, like os.Exit (don't use it), and approach it as a way to shut down the machine when it encounters a VM.

[thehowl]

I also tend to agree that it is not a good idea to add os.Exit to exit the smart contract. On top of this, this should exit the smart contract, not actually call an os.Exit -- because that would kill the program, even if it has goroutines or recover() calls -- so when this is called on gnoland the node would be shut down.

I prefer much more a defer-recover in the functions of the contract that need to be able to exit with a specific error than can be used to exit it.

[albttx]

guys... this was an April fool ... i guess it's failed 😂

[thehowl]

lol