search for: findlead

...} } I get something like this: ### New set: ### New set: ### New set: ### New set: ### New set: ### New set: a b ### New set: ### New set: c d e f ### New set: g ### New set: h ### New set: i j Why all the empty sets? Is this an artifact of the path compression? What does findLeader do? Does it return a member iterator that is at the beginning of the list of equivalence class members? The Doxygen documentation seems to indicate that it does not, but returns a member_iterator pointing to o. But then what is a "Leader" and why do I care?...

...the leader for the specified value that is /// in the set. If the member is not in the set, it is inserted, then /// returned. - const ElemTy &getOrInsertLeaderValue(const ElemTy &V) const { + const ElemTy &getOrInsertLeaderValue(const ElemTy &V) { member_iterator MI = findLeader(insert(V)); assert(MI != member_end() && "Value is not in the set!"); return *MI; -------------- next part -------------- A non-text attachment was scrubbed... Name: ec.patch Type: application/octet-stream Size: 676 bytes Desc: not available URL: <http://lists.llvm....

...n issue with dealing with next this way is that people adding new uses of next will probably not be using c++0x and therefore won't know it's ambiguous and that it needs to be qualified. There are also two issues with rvalue references and the STL: 1. EquivalenceClasses, in the insert and findLeader functions, it uses map functions which have versions taking rvalue references. This results in a compiler error because the private constructor of ECValue is inaccessible. The easiest fix is to explicitly call the constructor of ECValue before the insert/find calls. 2. There are numerous places...

...used. The carefully crafted C++ library should be aware of ADL issues. It should know when ADL is being used, and when it isn't, and use ADL purposefully, not accidentally. > There are also two issues with rvalue references and the STL: > > 1. EquivalenceClasses, in the insert and findLeader functions, it uses map functions which have versions taking rvalue references. This results in a compiler error because the private constructor of ECValue is inaccessible. The easiest fix is to explicitly call the constructor of ECValue before the insert/find calls. If I'm understanding the...

On Dec 2, 2009, at 6:54 AM, Howard Hinnant wrote: > I've completed a survey of llvm for unnecessary dependencies on > libstdc++, and on conflicts with the upcoming C++0X standard, and am > recommending several changes in the enclosed patch (created with svn > diff). Thanks, applied here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20091130/092102.html I

I've completed a survey of llvm for unnecessary dependencies on libstdc++, and on conflicts with the upcoming C++0X standard, and am recommending several changes in the enclosed patch (created with svn diff). Here is a summary of the patch: --- #include <cstdlib> added to LinkAllVMCore.h and LinkAllCodegenComponents.h to declare std::getenv. Changed next(...) to llvm::next(...) in