Issue 17911007: Have DispatchToMethod use base::internal::UnwrapTraits when dispatching

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 17911007: Have DispatchToMethod use base::internal::UnwrapTraits when dispatching (Closed)

Created:
7 years, 6 months ago by Ryan Sleevi

Modified:
7 years, 5 months ago

Reviewers:
darin (slow to review), awong

CC:
chromium-reviews, erikwright+watch_chromium.org

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

Have DispatchToMethod use base::internal::UnwrapTraits when dispatching When dispatching, have base::DispatchToMethod/DispatchToFunction use the base::internal::UnwrapTraits<> to properly unwrap the base::Tuple's wrapped argument. This ensures that methods that expect a "T*" can be properly dispatched when the tuple contains a scoped_refptr<T> without relying on implicit conversions. BUG=110610 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=208903