[Prospective vision] Optional Strict Memory Safety for Swift

By the way, we used to have these unchecked math operations available in all optimization modes: they were explicitly documented as having UB in case of overflow, and of course, they were named as follows:

  • unsafeAdding(_:)
  • unsafeSubtracting(_:)
  • unsafeMultiplied(by:)
  • unsafeDivided(by:)
1 Like