The "CAN'T REACH" comment is there because execution never reach that part of the code. If you write code there, it will never be executed. The process code performs a return without pushing any value on stack.

Signalling an error is safe if the error is never resumed. But you'll need the returnNoValue for performance intensive modification tracking.

On Wed, Jan 25, 2017 at 10:26 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:

2017-01-25 22:24 GMT+01:00 Denis Kudriashov <dionisiydk@gmail.com>:
For the Process hack, it's because the call-back was designed to return no value.

Now I am confused.��
Why anybody needs to return value from this method?��
And why there is ��"CAN'T REACH" comment��at the end of method?
Do you mean that method should never return?��
��
It may look like it works when returning a value but you will have uncommon crashes.

And is it safe to just signal error?��