Add ABORTMSG & ASSERTMSG

[ixje]

See neo-project/neo#2782 (comment)
I think there's a big upside in supporting this in terms of improved developer experience by having actual feedback on why the ABORT or ASSERT failed. Hence why I'm trying to keep this going

For example the reason(s) why sending funds to this NFT fails can actually be communicated back to the user without having to run a node yourself in order to be able to read the logs

[shargon]

@roman-khimov What do you think? I think that we need to move on on this topic

[roman-khimov]

I think it's good. Not sure which order of x and msg on the stack is more appropriate for ASSERTMSG (to make it easier for compilers to use it), but it'll solve the problem anyway.

[ixje]

@shargon seems like it can be then merged, right?

[AnnaShaleva]

We don't have this PR in the v3.6 list. Are we going to include it into 3.6?

[ixje]

We don't have this PR in the v3.6 list. Are we going to include it into 3.6?

I'm pushing for it because this feature is very very useful for the Hackathon (and in general) and very easy to implement (at least on the VM side)

[AnnaShaleva]

I'm pushing for it because this feature is very very useful for the Hackathon (and in general) and very easy to implement (at least on the VM side)

It's OK, I'm just wondering. I also like this feature.

[ixje]

@shargon ping ☝️