Shargon
Shargon
What's the sense if is not possible to use in a smart contract
One example is this one https://github.com/neo-project/neo-vm/pull/157 We need to be able to choose the logic acording to the height.
But vm are not able to receive different logic according to the version
You don't need to include the height, but you must include a way for allow to changing the opcode logic/versioning
The thing is if we find a bug in `CAT` or and optimization that could produce that the previous execution give different results, we need to be able to change...
I think we should create a `JumpTable` in neo-vm, to allow `ApplicationEngine` to change logic according to height. I can start with this if we are agree. With this change...
In my experience, reflection always it's slower, in your benchmarks you need to increase the time spend in get the structure from the cache, i think that it will be...
Is solved?
> Yep, https://github.com/neo-project/proposals/pull/126#discussion_r522309255 Maybe we can add just a note, *this syscall will compare against the callingScriptHash first..*?
> We need to explain what the contract is supposed to do and give the best practices for doing it in one step using CheckWitness. We can add a note...