[PATCH] Remove a bunch of weak vtables

[Juergen Ributzka]

  Creating the anchor function is only one possible approach that could be used. As the coding standard says we only need at least one out-of-line virtual method. This is actually not precise enough. We need at least one-out-of line virtual method and the first one of these defines the vtable location. Depending on the a particular implementation of a class we might not need the anchor method, because there is already another out-of-line virtual method. There is always the virtual destructor (implicit or explicit). I normally only use the anchor method when I don't want to use the destructor, because I want simple destructors to be inlined - if possible. Maybe we could summarize this as best practices and extend the documentation?

http://llvm-reviews.chandlerc.com/D2068