Support binding WeakPtr<> to methods with void return types.

This should give functionality similar to ScopedRunnableMethodFactory.

Note that binding a WeakPtr only make sense with methods with void return types.  If the return type is not void, then it is unclear what the function should return when the pointer is invalidated.

This code adds a compile time assert to check the return type.

BUG=35223
TEST=unittests

Review URL: http://codereview.chromium.org/7015064

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85549 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 4 insertions, 4 deletions

diff --git a/base/callback.h.pump b/base/callback.h.pump
index b565e38..cc45dd7 100644
--- a/base/callback.h.pump
+++ b/base/callback.h.pump
@@ -47,12 +47,12 @@ $var MAX_ARITY = 6
 //
 // /* Binding a normal function. */
 // int Return5() { return 5; }
-// base::Callback<int(int)> func_cb = base::Bind(&Return5);
-// LOG(INFO) << func_cb.Run(5);  // Prints 5.
+// base::Callback<int(void)> func_cb = base::Bind(&Return5);
+// LOG(INFO) << func_cb.Run();  // Prints 5.
 //
 // void PrintHi() { LOG(INFO) << "hi."; }
 // base::Closure void_func_cb = base::Bind(&PrintHi);
-// LOG(INFO) << void_func_cb.Run();  // Prints: hi.
+// void_func_cb.Run();  // Prints: hi.
 //
 // /* Binding a class method. */
 // class Ref : public RefCountedThreadSafe<Ref> {
@@ -191,7 +191,7 @@ $var MAX_ARITY = 6
 //
 // These are not features that are required in Chromium. Some of them, such as
 // allowing for reference parameters, and subtyping of functions, may actually
-// because a source of errors. Removing support for these features actually
+// become a source of errors. Removing support for these features actually
 // allows for a simpler implementation, and a terser Currying API.
 //
 //