@noxiouz points out that we don't need to check for a nil result from C.CString(), since an out-of-memory condition causes a runtime panic instead. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com> (github: nalind) Upstream-commit: 11fda783f85e1f6027c997c6b044c65288c89099 Component: engine