Table 80 documents container requirements in informal unexecutable
form.  The Container concept in 23.2.6.1 covers much of the same
ground in formal executable form.  Is there a reason not to remove the
redundant material from the table?  (The same question can be raised
for other places where table content and concepts overlap.)

It seems to me that redundant specifications for specific
functionality in different parts of the standard open the door to
inconsistency, cause bloat, and basically set a bad example.  Is there
a reason why information in concepts can't be removed from tables?

Thanks,

Scott

--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]