You can use pools if you want to. For example, if you’re iterating over a lot of objects the “standard” approach is to allocate a subpool before you start the iteration, and clear it at the start of each iteration, so that memory usage doesn’t grow, and operations tend to take O(1) memory rather than O(n).

You don’t need to do that now if you don’t want to though.

I agree that having to worry about this at all isn’t terribly Perlish (although, I guess, not much more so than having to worry about references, cyclic references, weakening them, and so on).

The sort of stuff I’m immediately looking at is getting the API to support named parameters for calls as well as the positional parameters, and, where possible, to supply default values for those parameters so that your Perl code can be simpler and more readable. I’m working on a patch (which will be committed) for that at the moment.