Remove reference to nullptr to avoid compiler seeing ambiguity in gcc-4.4

build. The issue is that gcc below 4.6 require us to explicitly define nullptr,
and our explicit definition allows a potential confusion between
nullptr->unique_ptr<string> and
nullptr->char *->grpc::string->unique_ptr<string>

1 files changed, 1 insertions, 1 deletions

diff --git a/test/cpp/end2end/end2end_test.cc b/test/cpp/end2end/end2end_test.cc
index f0d9f75214..59e1173c5d 100644
--- a/test/cpp/end2end/end2end_test.cc
+++ b/test/cpp/end2end/end2end_test.cc
@@ -98,7 +98,7 @@ void CheckAuthContext(T* context) {
 
 class TestServiceImpl : public ::grpc::cpp::test::util::TestService::Service {
  public:
-  TestServiceImpl() : signal_client_(false), host_(nullptr) {}
+  TestServiceImpl() : signal_client_(false), host_() {}
   explicit TestServiceImpl(const grpc::string& host) : signal_client_(false), host_(new grpc::string(host)) {}
 
   Status Echo(ServerContext* context, const EchoRequest* request,