[cfe-commits] [libcxx] r136547 - /libcxx/trunk/include/ext/slist

Howard Hinnant hhinnant at apple.com
Sat Jul 30 08:57:40 PDT 2011


It is not clear to me that the addition of ext/slist is a path we want to take with libc++.  It bloats the library.  It requires debugging, maintenance, and unit tests.  There exists a C++11 replacement that is well specified and well tested.

We don't need another C++03 std::lib.  Plenty of those already exists.  libc++ was envisioned to be a C++0x library.  There are tons of old extensions libc++ doesn't have.  Are we going to implement all of them?  Even the ones that have C++11 replacements?  Even  the ones that introduce their own set of problems?  Where do we draw the line?

libc++ had drawn the line at the hash containers.  I am uneasy with the introduction of slist.  And I am adamant that such an extension not be introduced without discussion.

Please remove slist for now.  Please feel free to start a thread on cfe-dev regarding whether we should introduce it.

Howard




More information about the cfe-commits mailing list