drop android stuff

Author: hyp

stdlib/public/Platform/Android.swift

@@ -11,78 +11,3 @@
 //===----------------------------------------------------------------------===//
 
 @_exported import SwiftAndroid // Clang module
-
-@available(swift, deprecated: 3.0, message: "Please use 'Double.pi' or '.pi' to get the value of correct type and avoid casting.")
-public let M_PI = Double.pi
-@available(swift, deprecated: 3.0, message: "Please use 'Double.pi / 2' or '.pi / 2' to get the value of correct type and avoid casting.")
-public let M_PI_2 = Double.pi / 2
-@available(swift, deprecated: 3.0, message: "Please use 'Double.pi / 4' or '.pi / 4' to get the value of correct type and avoid casting.")
-public let M_PI_4 = Double.pi / 4
-
-@available(swift, deprecated: 3.0, message: "Please use 2.squareRoot()'.")
-public let M_SQRT2 = 2.squareRoot()
-
-@available(swift, deprecated: 3.0, message: "Please use 0.5.squareRoot()'.")
-public let M_SQRT1_2 = 0.5.squareRoot()
-
-@available(swift, deprecated: 3.0, message: "Please use 'T.radix' to get the radix of a FloatingPoint type 'T'.")
-public let FLT_RADIX = Double.radix
-
-//  Where does the 1 come from? C counts the usually-implicit leading
-//  significand bit, but Swift does not. Neither is really right or wrong.
-@available(swift, deprecated: 3.0, message: "Please use 'Float.significandBitCount + 1'.")
-public let FLT_MANT_DIG = Float.significandBitCount + 1
-
-//  Where does the 1 come from? C models floating-point numbers as having a
-//  significand in [0.5, 1), but Swift (following IEEE 754) considers the
-//  significand to be in [1, 2). This rationale applies to FLT_MIN_EXP
-//  as well.
-@available(swift, deprecated: 3.0, message: "Please use 'Float.greatestFiniteMagnitude.exponent + 1'.")
-public let FLT_MAX_EXP = Float.greatestFiniteMagnitude.exponent + 1
-
-@available(swift, deprecated: 3.0, message: "Please use 'Float.leastNormalMagnitude.exponent + 1'.")
-public let FLT_MIN_EXP = Float.leastNormalMagnitude.exponent + 1
-
-@available(swift, deprecated: 3.0, message: "Please use 'Float.greatestFiniteMagnitude' or '.greatestFiniteMagnitude'.")
-public let FLT_MAX = Float.greatestFiniteMagnitude
-
-@available(swift, deprecated: 3.0, message: "Please use 'Float.ulpOfOne' or '.ulpOfOne'.")
-public let FLT_EPSILON = Float.ulpOfOne
-
-@available(swift, deprecated: 3.0, message: "Please use 'Float.leastNormalMagnitude' or '.leastNormalMagnitude'.")
-public let FLT_MIN = Float.leastNormalMagnitude
-
-@available(swift, deprecated: 3.0, message: "Please use 'Float.leastNonzeroMagnitude' or '.leastNonzeroMagnitude'.")
-public let FLT_TRUE_MIN = Float.leastNonzeroMagnitude
-
-
-//  Where does the 1 come from? C counts the usually-implicit leading
-//  significand bit, but Swift does not. Neither is really right or wrong.
-@available(swift, deprecated: 3.0, message: "Please use 'Double.significandBitCount + 1'.")
-public let DBL_MANT_DIG = Double.significandBitCount + 1
-
-//  Where does the 1 come from? C models floating-point numbers as having a
-//  significand in [0.5, 1), but Swift (following IEEE 754) considers the
-//  significand to be in [1, 2). This rationale applies to DBL_MIN_EXP
-//  as well.
-@available(swift, deprecated: 3.0, message: "Please use 'Double.greatestFiniteMagnitude.exponent + 1'.")
-public let DBL_MAX_EXP = Double.greatestFiniteMagnitude.exponent + 1
-
-@available(swift, deprecated: 3.0, message: "Please use 'Double.leastNormalMagnitude.exponent + 1'.")
-public let DBL_MIN_EXP = Double.leastNormalMagnitude.exponent + 1
-
-@available(swift, deprecated: 3.0, message: "Please use 'Double.greatestFiniteMagnitude' or '.greatestFiniteMagnitude'.")
-public let DBL_MAX = Double.greatestFiniteMagnitude
-
-@available(swift, deprecated: 3.0, message: "Please use 'Double.ulpOfOne' or '.ulpOfOne'.")
-public let DBL_EPSILON = Double.ulpOfOne
-
-@available(swift, deprecated: 3.0, message: "Please use 'Double.leastNormalMagnitude' or '.leastNormalMagnitude'.")
-public let DBL_MIN = Double.leastNormalMagnitude
-
-@available(swift, deprecated: 3.0, message: "Please use 'Double.leastNonzeroMagnitude' or '.leastNonzeroMagnitude'.")
-public let DBL_TRUE_MIN = Double.leastNonzeroMagnitude
-
-public let M_LN2 = SwiftAndroid.M_LN2
-public let M_LOG10E = SwiftAndroid.M_LOG10E
-public let M_2_SQRTPI = SwiftAndroid.M_2_SQRTPI