Make adding and subtracting gfx:: point types simpler.

ui/gfx/rect.h

Index: ui/gfx/rect.h
diff --git a/ui/gfx/rect.h b/ui/gfx/rect.h
index 64f35b1fe8adde6d9b0e0de6e01b1501ce7e71d3..6c812f87279aa756d7949236422b3d6847a88950 100644
--- a/ui/gfx/rect.h
+++ b/ui/gfx/rect.h
@@ -68,19 +68,19 @@ class UI_EXPORT Rect : public RectBase<Rect, Point, Size, Insets, int> {
   CGRect ToCGRect() const;
 #endif
 
-  RectF ToRectF() const WARN_UNUSED_RESULT {
-    return RectF(origin().x(), origin().y(), size().width(), size().height());
-  }
-
   RectF Scale(float scale) const WARN_UNUSED_RESULT {
     return Scale(scale, scale);
   }
 
   RectF Scale(float x_scale, float y_scale) const WARN_UNUSED_RESULT {
-    return ToRectF().Scale(x_scale, y_scale);
+    return static_cast<RectF>(*this).Scale(x_scale, y_scale);
   }
 
   std::string ToString() const;
+
+  operator RectF() const {

[sky, 2012/10/01 21:02:20]

Why is this better than ToRectF?

[danakj, 2012/10/01 21:55:34]

So you don't have to cast all the ints to floats explicitly every time you have
some floating point values in the equation.

float f; int i;
float f2 = f + i; // does not need static_cast<float>(i).

RectF f; Rect i;
PointF f2 = f.origin() + i.origin(); // would need i.ToRectF().origin()

If I want to add something to a PointF, I don't care if it is a Point or a
PointF. I feel ToRectF() just decreases the signal to noise ratio of the code.

+    return RectF(origin().x(), origin().y(), size().width(), size().height());
+  }
 };
 
 #if !defined(COMPILER_MSVC)