"typedef Foo Bar" -> "using Bar = Foo" in //mojo/edk/....

mojo/edk/system/data_pipe_impl_unittest.cc

Index: mojo/edk/system/data_pipe_impl_unittest.cc
diff --git a/mojo/edk/system/data_pipe_impl_unittest.cc b/mojo/edk/system/data_pipe_impl_unittest.cc
index 17021f35ca7450e1589349c79ba59bc49cff5c4e..3a774881bb4ce14a2f5fd1d4e03950d68b02b86e 100644
--- a/mojo/edk/system/data_pipe_impl_unittest.cc
+++ b/mojo/edk/system/data_pipe_impl_unittest.cc
@@ -549,11 +549,11 @@ class RemoteConsumerDataPipeImplTestHelper2
 
 // Test case instantiation -----------------------------------------------------
 
-typedef testing::Types<LocalDataPipeImplTestHelper,
-                       RemoteProducerDataPipeImplTestHelper,
-                       RemoteConsumerDataPipeImplTestHelper,
-                       RemoteProducerDataPipeImplTestHelper2,
-                       RemoteConsumerDataPipeImplTestHelper2> HelperTypes;
+using HelperTypes = testing::Types<LocalDataPipeImplTestHelper,

[jamesr, 2015/05/22 18:16:04]

woah, do i wanna look at what this is?

[viettrungluu, 2015/05/22 18:24:27]

The short answer is no. The long answer is type-parametrized tests. (Fun!)

+                                   RemoteProducerDataPipeImplTestHelper,
+                                   RemoteConsumerDataPipeImplTestHelper,
+                                   RemoteProducerDataPipeImplTestHelper2,
+                                   RemoteConsumerDataPipeImplTestHelper2>;
 
 TYPED_TEST_CASE(DataPipeImplTest, HelperTypes);