Resolve an ambiguous function call by casting to StringPiece::size_type

Resolve an ambiguous function call error in string_piece_unittest.cc

BUG=
TEST=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=117050

[Peter Beverloo, 2012-01-10 14:16:52]

Since brettw's on leave, and you're back(!), mind having a look Evan?

The Android NDK compiler interpreters the string type as const char*, causing a
compile error due to an ambiguous function call. See this log from the builder:
http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Linux%20Android/...

[Peter Beverloo, 2012-01-10 16:11:36]

Working link to the output:
http://goo.gl/AnIA5

[Evan Martin, 2012-01-10 16:15:59]

lgtm

LGTM with whitespace fixed

I admit I don't fully understand what's going on here; I wonder if just making
the value explicitly unsigned would be sufficient, like seen in other tests:
http://codesearch.google.com/codesearch#search/&exact_package=chromium&q=%5Cd...

but if this works it seems good too.

http://codereview.chromium.org/9167008/diff/1/base/string_piece_unittest.cc
File base/string_piece_unittest.cc (right):

http://codereview.chromium.org/9167008/diff/1/base/string_piece_unittest.cc#n...
base/string_piece_unittest.cc:668: static_cast<StringPiece::size_type>(0)));
Can you indent this to match the opening paren like the line above?

[Peter Beverloo, 2012-01-10 16:24:54]

Using "0U" works fine indeed, thank you!  I chose "0U" over "0u" to match the
rest of this file.  Since this is a code change, could you give a new lgtm?

[Evan Martin, 2012-01-10 16:55:01]

lgtm

[commit-bot: I haz the power, 2012-01-10 16:57:10]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/peter@chromium.org/9167008/4001

[commit-bot: I haz the power, 2012-01-10 18:00:44]

Change committed as 117050