swift-reflection-dump: use elaborated type name

compnerd · compnerd · commit a2ff73fd9a91 · 2019-02-24T15:40:00.000-08:00
cl is unable to differentiate between the `swift::ReflectionContext` and
`swift::reflection::ReflectionContext`.  Use the elaborated typename to
uniquely identify the type.  This allows us to build
`swift-reflection-dump` with cl again.
diff --git a/tools/swift-reflection-dump/swift-reflection-dump.cpp b/tools/swift-reflection-dump/swift-reflection-dump.cpp
@@ -80,7 +80,7 @@ static T unwrap(llvm::Expected<T> value) {
 }
 
 using NativeReflectionContext
-  = ReflectionContext<External<RuntimeTarget<sizeof(uintptr_t)>>>;
+    = swift::reflection::ReflectionContext<External<RuntimeTarget<sizeof(uintptr_t)>>>;
 
 class ObjectMemoryReader : public MemoryReader {
   const std::vector<const ObjectFile *> &ObjectFiles;

Original file line number	Diff line number	Diff line change
`@@ -80,7 +80,7 @@ static T unwrap(llvm::Expected<T> value) {`
`80`	`80`	`}`
`81`	`81`
`82`	`82`	`using NativeReflectionContext`
`83`		`- = ReflectionContext<External<RuntimeTarget<sizeof(uintptr_t)>>>;`
	`83`	`+ = swift::reflection::ReflectionContext<External<RuntimeTarget<sizeof(uintptr_t)>>>;`
`84`	`84`
`85`	`85`	`class ObjectMemoryReader : public MemoryReader {`
`86`	`86`	`const std::vector<const ObjectFile *> &ObjectFiles;`