jingham accepted this revision. jingham added a comment. This revision is now accepted and ready to land.
This bug has been there since the first llvm.org checkin. I'm curious, did it actually cause a problem or did you just see it while reading? The patch is right. Most of the other uses elide storing the position the non-unique elements got moved to, and does "indexes.erase(std::unique...)" but either form is fine by me. https://reviews.llvm.org/D36126 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
