[Bug libstdc++/21770] New: rebinding allocator::value type vs. container::value_type

["bkoz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

Ami pointed this out to me a while ago. It seems as if we need to be able to
support  things like:

std::vector<int, std::allocator<char> > 

which was news to me. The current implementation is ... not so good about this.

This is a QoI issue, where Dinkumware and RW do this.

So, implement, figure out a way to test this, and apply consistently for all
containers.

-- 
           Summary: rebinding allocator::value type vs.
                    container::value_type
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bkoz at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21770