Inline in_bounds().

It's a tiny function called from many tight loops.  Inlining it gives ~1%
speedup in non-flto builds.

1 files changed, 0 insertions, 24 deletions

diff --git a/crawl-ref/source/coord.cc b/crawl-ref/source/coord.cc
index f9537a6213..203fdc09b5 100644
--- a/crawl-ref/source/coord.cc
+++ b/crawl-ref/source/coord.cc
@@ -28,30 +28,6 @@ bool adjacent(const coord_def& p1, const coord_def& p2)
     return grid_distance(p1, p2) <= 1;
 }
 
-bool in_bounds_x(int x)
-{
-    return (x > X_BOUND_1 && x < X_BOUND_2);
-}
-
-bool in_bounds_y(int y)
-{
-    return (y > Y_BOUND_1 && y < Y_BOUND_2);
-}
-
-// Returns true if inside the area the player can move and dig (ie exclusive).
-bool in_bounds(int x, int y)
-{
-    return (x > X_BOUND_1 && x < X_BOUND_2 && y > Y_BOUND_1 && y < Y_BOUND_2);
-}
-
-// Returns true if inside the area the player can map (ie inclusive).
-// Note that terrain features should be in_bounds() leaving an outer
-// ring of rock to frame the level.
-bool map_bounds(int x, int y)
-{
-    return (x >= X_BOUND_1 && x <= X_BOUND_2 && y >= Y_BOUND_1 && y <= Y_BOUND_2);
-}
-
 bool map_bounds_with_margin(coord_def p, int margin)
 {
     return (p.x >= X_BOUND_1 + margin && p.x <= X_BOUND_2 - margin