Fix a couple PDB vtable bugs #7825
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started digging into some vtable issues and there seem to be quite a few beyond just these trivial ones.
QualifiedNamedefault to::separator like docs say it should which fixes VTable struct being incorrectly defined without::e.g.MultiDerivedVTableMultiDerived::`vftable'{for `InterfaceB'}was getting incorrectly parsed asvftable'{for `InterfaceB::VTableTest binaries: pdb-vtable.zip
Before:

After:
