Comment 1 for bug 961547

So, I ran this idea past "top people" and this is the answer I got.

This isn't a bad idea. However, it's very dependent upon the way Swift works now.

If, for example, we implemented container splitting, returning such a value (and/or keeping it up to date), might prove too complicated.

Container splitting would allow the limits in number of objects per container to go away. It would also result in containers having more than a single database. Swift having to return this value after container splitting is done might create more complexity than we want.