Skip to content

Commit 612b49d

Browse files
amartini51natecook1000
authored andcommitted
Fix spelling of init?(exactly:) in prose. (#17483)
1 parent de5db38 commit 612b49d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

stdlib/public/core/Integers.swift.gyb

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1348,16 +1348,16 @@ extension Numeric {
13481348
///
13491349
/// Use the `init?(exactly:)` initializer to create a new instance after
13501350
/// checking whether the passed value is representable. Instead of trapping on
1351-
/// out-of-range values, using the failable `exact` initializer results in
1352-
/// `nil`.
1351+
/// out-of-range values, using the failable `init?(exactly:)`
1352+
/// initializer results in `nil`.
13531353
///
13541354
/// let x = Int16(exactly: 500)
13551355
/// // x == Optional(500)
13561356
///
13571357
/// let y = Int8(exactly: 500)
13581358
/// // y == nil
13591359
///
1360-
/// When converting floating-point values, the `init?(exact:)` initializer
1360+
/// When converting floating-point values, the `init?(exactly:)` initializer
13611361
/// checks both that the passed value has no fractional part and that the
13621362
/// value is representable in the resulting type.
13631363
///

0 commit comments

Comments
 (0)