Avoid warnings due to trailing backslash

I appreciate the elegance of using `\` and `/` to create ASCII art, but trailing backslashes in a `//` comment generates a lot of warnings with some compilers:

```
INFO: From Compiling src/core/lib/channel/promise_based_filter.cc:
In file included from external/com_github_grpc_grpc/src/core/lib/surface/server.h:48,
                 from external/com_github_grpc_grpc/src/core/lib/surface/call.h:53,
                 from external/com_github_grpc_grpc/src/core/lib/channel/promise_based_filter.h:65,
                 from external/com_github_grpc_grpc/src/core/lib/channel/promise_based_filter.cc:17:
external/com_github_grpc_grpc/src/core/lib/channel/call_tracer.h:47:1: warning: multi-line comment [-Wcomment]
   47 | //                      /          \
      | ^
external/com_github_grpc_grpc/src/core/lib/channel/call_tracer.h:49:1: warning: multi-line comment [-Wcomment]
   49 | //                                /             \
      | ^
```
pull/35464/head
Carlos O'Ryan 1 year ago committed by GitHub
parent c112dd7054
commit 18a7f6b8e6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 4
      src/core/lib/channel/call_tracer.h

@ -44,9 +44,9 @@ namespace grpc_core {
// The interface hierarchy is as follows - // The interface hierarchy is as follows -
// CallTracerAnnotationInterface // CallTracerAnnotationInterface
// / \ // | |
// ClientCallTracer CallTracerInterface // ClientCallTracer CallTracerInterface
// / \ // | |
// CallAttemptTracer ServerCallTracer // CallAttemptTracer ServerCallTracer
// The base class for all tracer implementations. // The base class for all tracer implementations.

Loading…
Cancel
Save