Temporaries are pieces of information reserving resources, created usually on explicit requests and evading general resource management mechanisms. Most of the time, temporaries will block resources (commonly memory) allocated for immediate function return values (consider a function concatenating two strings and allocating memory for storing the concatenation result and returning that concatenation result).
Since temporaries do not submit to regular resource management mechanisms, applications interested in using interfaces that may create temporaries need to setup special resource deallocation mechanisms for exactly temporaries blocked resources deallocation purposes.
No mechanism withing the libx1f4i0 interpreters create temporaries, only application may create temporaries (with respect to the program execution and expression evaluation, libraries, even those provided by libx1f4i0, are part of the application).
Applications are expected to either setup for temporaries (eventual) deallocation or refrain from using interfaces creating temporaries altogether.
For immediate temporaries deallocation applications may consider step by step program execution. Such program execution mode provides for the opportunity to free the resources blocked by temporaries as soon as they are no longer needed.
See Step By Step Imperative Program Execution.
See Step By Step Procedural Program Execution.