[stdlib] Don’t force-inline Character.== and .<

The code to compare character values can be huge; it doesn’t seem a good idea to forcibly inline it. The @inline(__always) here can make specialized Set<Character> operations balloon 10x their current size with unrelated modifications in Set.

The code size bloat doesn’t always happen; I *guess* that _fastPaths inside String.== cause unintuitive inlining decisions in callers.

Author: lorentey

stdlib/public/core/Character.swift

@@ -448,7 +448,6 @@ internal var _minASCIICharReprBuiltin: Builtin.Int63 {
 
 extension Character : Equatable {
   @inlinable
-  @inline(__always)
   public static func == (lhs: Character, rhs: Character) -> Bool {
     let l0 = lhs._smallUTF16
     if _fastPath(l0 != nil), let l = l0?._storage {
@@ -467,7 +466,6 @@ extension Character : Equatable {
 
 extension Character : Comparable {
   @inlinable
-  @inline(__always)
   public static func < (lhs: Character, rhs: Character) -> Bool {
     let l0 = lhs._smallUTF16
     if _fastPath(l0 != nil), let l = l0?._storage {