mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
2fc5cbdc14
This replaces swiftMSVCRT with swiftCRT. The big difference here is that the `visualc` module is no longer imported nor exported. The `visualc` module remains in use for a singular test wrt availability, but this should effectively remove the need for the `visualc` module. The difference between the MSVCRT and ucrt module was not well understood by most. MSVCRT provided ucrt AND visualc, combining pieces of the old MSVCRT and the newer ucrt. The ucrt module is what you really wanted most of the time, however, would need to use MSVCRT for the convenience aliases for type-generic math and the deprecated math constants. Unfortunately, we cannot shadow the `ucrt` module and create a Swift SDK overlay for ucrt as that seems to result in circular dependencies when processing the `_Concurrency` module. Although this makes using the C library easier for most people, it has a more important subtle change: it cleaves the dependency on visualc. This means that this enables use of Swift without Visual Studio for the singular purpose of providing 3 header files. Additionally, it removes the need for the installation of 2 of the 4 support files. This greatly simplifies the deployment process on Windows.
89 lines
4.5 KiB
Swift
89 lines
4.5 KiB
Swift
//===----------------------------------------------------------------------===//
|
|
//
|
|
// This source file is part of the Swift.org open source project
|
|
//
|
|
// Copyright (c) 2014 - 2017 Apple Inc. and the Swift project authors
|
|
// Licensed under Apache License v2.0 with Runtime Library Exception
|
|
//
|
|
// See https://swift.org/LICENSE.txt for license information
|
|
// See https://swift.org/CONTRIBUTORS.txt for the list of Swift project authors
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
@_exported import ucrt // 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 = ucrt.M_LN2
|
|
public let M_LOG10E = ucrt.M_LOG10E
|
|
public let M_2_SQRTPI = ucrt.M_2_SQRTPI
|