From c5846378ab2789f82510bbc80ac5a1a8dacddb6e Mon Sep 17 00:00:00 2001
From: Beman Dawes
A. As an aid to writing test cases and debugging displays. One of the
progenitors had use_count(), and it was useful in tracking down bugs in a
complex project that turned out to have cyclic-dependencies.
Q. Why doesn't shared_ptr specify complexity requirements?
+A. Because complexity limit implementors and complicate the specification without apparent benefit to
+shared_ptr users. For example, error-checking implementations might become non-conforming if they
+had to meet stringent complexity requirements.
Q. Why doesn't shared_ptr provide (your pet feature here)?
+A. Because (your pet feature here) would mandate a reference counted (or a link-list, or ...) implementation. This is not the intent.
+[Provided by Peter Dimov]
+
Revised 13 July, 2001