Currently, if go2cStr meets zero byte in the middle or in the end of the string, it stops early (and also oddly produces two zero bytes instead of one).
Instead, it should report error that the input string is incorrect. Everywhere where we call go2cStr, we should check error and report it to user.
Currently, if go2cStr meets zero byte in the middle or in the end of the string, it stops early (and also oddly produces two zero bytes instead of one).
Instead, it should report error that the input string is incorrect. Everywhere where we call go2cStr, we should check error and report it to user.