This function frees global resources (grids, cache of +init files). It should be called typically before process termination, and after having freed PJ and PJ_CONTEXT objects.
This crate runs proj_cleanup on every Drop for Proj and ProjBuilder. So if you have two Proj instances in your application and one gets dropped, we'll run proj_cleanup even though the other Proj is still alive. My interpretation of the documentation for proj_cleanup (above) is that we should only run proj_cleanup after all other PROJ objects and contexts have been freed.
If this is the case, we'd need to think through how to accomplish this, as Rust has no way to automatically run code when a process ends. We'd have to do some sort of reference counting and only run proj_cleanup if we know there are now Proj instances alive
This crate runs
proj_cleanupon everyDropforProjandProjBuilder. So if you have twoProjinstances in your application and one gets dropped, we'll runproj_cleanupeven though the otherProjis still alive. My interpretation of the documentation forproj_cleanup(above) is that we should only runproj_cleanupafter all other PROJ objects and contexts have been freed.If this is the case, we'd need to think through how to accomplish this, as Rust has no way to automatically run code when a process ends. We'd have to do some sort of reference counting and only run
proj_cleanupif we know there are nowProjinstances alive