Hi all,
Just finished debugging a memory clobbering bug resulting from using
SmallVectorImpl directly without realizing this is a bad idea (aside: I was
using it directly because llvm::sys::path::append()'s first argument is a
SmallVectorImpl<char>). A note in the docs about not using SmallVectorImpl
directly would be nice but could we go further and make SmallVectorImpl's
constructors not public? Is there a reason why they're public right now?
--
Edwin Vane
Software Developer
SSG/DPD/ECDL/ArBB
Phone: +1 519 772 2567
iNET: 87722567
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20120120/7ed97847/attachment.html>