bugfix: don't return the value on `setValue`

[alcueca]

I might be wrong, but given the function interface, setValue is not expected to return a value.

If we don't return on setValue, then getValue gets executed afterwards, returning value.

To test, you can do this:

[devtooligan]

Thanks for opening this.

Great catch!

However, this solution using the stop opcode here is preferred. That one was just merg ed.

What your solution does is to actually return whatever is stored at 0x00 (which in this case will be 0x0 so it doesn't really matter but we should still be using stop).

[alcueca]

Thank you, I hadn't got yet to the stop opcode in the tutorial :D