Add more missing closing namespace comments.

Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previously I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and 'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build clang_use_chrome_plugins=0 fastbuild=1 component=shared_library' build/gyp_chromium

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
R=jochen@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/be94d60086b4453ea0f3769a9a3e85feb0cfbfe9

[Nico, 2016-01-23 21:56:34]

Description was changed from

==========
Add more missing closing namespace comments.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previoulsy I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json


BUG=580787, 403854
==========

to

==========
Add more missing closing namespace comments.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previoulsy I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium 

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
==========

[Nico, 2016-01-23 21:57:36]

Description was changed from

==========
Add more missing closing namespace comments.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previoulsy I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium 

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
==========

to

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previoulsy I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium 

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
==========

[Nico, 2016-01-23 21:58:51]

thakis@chromium.org changed reviewers:
+ jochen@chromium.org

[Nico, 2016-01-23 21:58:56]

jochen, please quickly review this small 1099 file CL.

If you really want to look at the change, click "raw diff", I could scroll
through everything in a few minutes there.

This removes a few more lines than it adds due to things like
https://codereview.chromium.org/1627713002/diff/1/third_party/WebKit/Source/c...

[Nico, 2016-01-23 21:59:43]

Description was changed from

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previoulsy I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium 

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
==========

to

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previously I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium 

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
==========

[jochen (gone - plz use gerrit), 2016-01-25 10:00:32]

lgtm with comment addressed

https://codereview.chromium.org/1627713002/diff/1/third_party/WebKit/Source/c...
File third_party/WebKit/Source/core/dom/DocumentParser.cpp (right):

https://codereview.chromium.org/1627713002/diff/1/third_party/WebKit/Source/c...
third_party/WebKit/Source/core/dom/DocumentParser.cpp:117: } // namespace blink;
can you strip the ; from the comment?

[commit-bot: I haz the power, 2016-01-25 15:12:44]

Description was changed from

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previously I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium 

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
==========

to

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previously I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
R=jochen@chromium.org

Committed: https://crrev.com/be94d60086b4453ea0f3769a9a3e85feb0cfbfe9
Cr-Commit-Position: refs/heads/master@{#371243}
==========

[commit-bot: I haz the power, 2016-01-25 15:12:48]

Patchset 2 (id:??) landed as
https://crrev.com/be94d60086b4453ea0f3769a9a3e85feb0cfbfe9
Cr-Commit-Position: refs/heads/master@{#371243}

[Nico, 2016-01-25 15:13:28]

Description was changed from

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previously I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
R=jochen@chromium.org

Committed: https://crrev.com/be94d60086b4453ea0f3769a9a3e85feb0cfbfe9
Cr-Commit-Position: refs/heads/master@{#371243}
==========

to

==========
Add more missing closing namespace comments.

This helps clang-format a bit (without these, it removes the empty
line before the namespace's closing '}'), and since we want these
comments anyway, just add them.

Patch created by running (in src/out/Release):
time ~/src/llvm-rw/tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
    -checks=-*,google-readability-namespace-comments -p ../.. \
    -clang-tidy-binary ~/src/llvm-build/bin/clang-tidy \
    -header-filter third_party/WebKit/Source -j8 -fix third_party/WebKit/Source

Previously I created compile_commands.json by running (in src/):
    ninja -C out/Release/ -t compdb objcxx cxx > compile_commands.json

To let clang-tidy and clang agree on which revision should be used for
precompiled
header files (I did this on Mac), I gypped like so and built 'blink' and
'webcore' normally
before running clang-tidy:

GYP_DEFINES='make_clang_dir=/Users/thakis/src/llvm-build
clang_use_chrome_plugins=0 fastbuild=1 component=shared_library'
build/gyp_chromium

This is like https://codereview.chromium.org/1629693002/, but for all of blink.
No behavior change.

BUG=580787, 403854
R=jochen@chromium.org

Committed:
https://chromium.googlesource.com/chromium/src/+/be94d60086b4453ea0f3769a9a3e...
==========

[Nico, 2016-01-25 15:13:33]

Committed patchset #2 (id:20001) manually as
be94d60086b4453ea0f3769a9a3e85feb0cfbfe9.