WTF::OwnPtr should behave similarly with the rest of WTF smart pointers

WTF::OwnPtr should behave similarly with the rest of WTF smart pointers

Before the change OwnPtr could take either the pointer type or the pointed-to type, which was bad for the following reasons:
- It distinguished OwnPtr behaviour from other WTF smart pointer classes behaviour (so it was confusing for the Client).
- It was potential error-prone as it actually modified the type given by the Client in opaque way.

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=157328

[Mikhail, 2013-09-05 15:33:39]

Could you please have a look?

[tkent, 2013-09-05 21:57:37]

lgtm

[commit-bot: I haz the power, 2013-09-05 21:57:58]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mikhail.pozdnyakov@intel.com/23960005/1

[commit-bot: I haz the power, 2013-09-05 23:01:00]

Change committed as 157328

[abarth-chromium, 2013-09-06 05:13:12]

https://codereview.chromium.org/23960005/diff/1/Source/wtf/OwnPtr.h
File Source/wtf/OwnPtr.h (left):

https://codereview.chromium.org/23960005/diff/1/Source/wtf/OwnPtr.h#oldcode46
Source/wtf/OwnPtr.h:46: typedef typename RemovePointer<T>::Type ValueType;
Is RemovePointer used anywhere else?  Perhaps we can remove it.

[Mikhail, 2013-09-06 07:58:55]

On 2013/09/06 05:13:12, abarth wrote:
> https://codereview.chromium.org/23960005/diff/1/Source/wtf/OwnPtr.h
> File Source/wtf/OwnPtr.h (left):
> 
> https://codereview.chromium.org/23960005/diff/1/Source/wtf/OwnPtr.h#oldcode46
> Source/wtf/OwnPtr.h:46: typedef typename RemovePointer<T>::Type ValueType;
> Is RemovePointer used anywhere else?  Perhaps we can remove it.

It's used also in CrossThreadCopier and RetainPtr.