Sure! What I meant is that container reuse is technically just an implementation detail, so you can use it for caching in-memory, but only while the implementation remains this way.
For example if they were to spin up a new container for every single function call, this wouldn’t do anything. Technically we’re supposed to treat FaaS this way, completely stateless, and as if it was fresh each time, so it’s sort of just a hack (works though!).