| Index: third_party/WebKit/Source/wtf/ScopedLogger.md
|
| diff --git a/third_party/WebKit/Source/wtf/ScopedLogger.md b/third_party/WebKit/Source/wtf/ScopedLogger.md
|
| index 36b67f0eb0ddde0fd48f7dcfd6f8775b87f96314..5ea0d0fdffcd7f7150461eb5119b485a1ad2b55a 100644
|
| --- a/third_party/WebKit/Source/wtf/ScopedLogger.md
|
| +++ b/third_party/WebKit/Source/wtf/ScopedLogger.md
|
| @@ -89,10 +89,8 @@ The ScopedLogger macros work in debug builds by default. They are compiled out
|
| of release builds, unless your `GYP_DEFINES` or GN args file includes one of the
|
| following:
|
|
|
| -* `dcheck_always_on`: enables assertions and logging
|
| -* `blink_logging_always_on`: enables logging, but not assertions
|
| -
|
| -(These are the same rules that govern `WTF_LOG` and other WTF logging macros.)
|
| +* `dcheck_always_on`: enables assertions and ScopedLogger
|
| +* `blink_logging_always_on`: enables ScopedLogger, but not assertions
|
|
|
| The macro names are cumbersome to type, but most editors can be configured to
|
| make this easier. For example, you can add the following to a Sublime Text key
|
|
|