RE: svn commit: r1555350 -/subversion/trunk/subversion/libsvn_client/mtcc.c
From: Bert Huijben <bert_at_qqmail.nl>
Date: Sat, 4 Jan 2014 21:47:43 +0100
You only know this for the success path. The fs api should hide these details..
There is no way we can document these guarantees for public APIs and really assume that all existing and future users follow all these new requirements for a new Fs layer cache.
We had similar caches in the past, but hid the ugly details by installing cleanup handlers...
We should really look at this well before 1.9, as adding such requirements is a breaking change. And the commit API already existed since well before 1.0 without these pool requirements. Strict dual pools are only common since 1.7, but especially generated bindings (like swig) have strange pool handling much longer.
This is an archived mail posted to the Subversion Dev mailing list.