Currently, corto creates temporary objects when serializing between content types. This can cause unwanted side-effects, like lifecycle hooks being called while serializing. Instead of using objects, corto should use the corto_mem_new API to allocate a chunk of memory big enough to act as intermediate value.
Currently, corto creates temporary objects when serializing between content types. This can cause unwanted side-effects, like lifecycle hooks being called while serializing. Instead of using objects, corto should use the
corto_mem_newAPI to allocate a chunk of memory big enough to act as intermediate value.