When I cmd click the split function in Xcode, it takes me to the header file. This is what it reads
public func split(maxSplit: Int = default, allowEmptySlices: Bool = default, @noescape isSeparator: (Self.Generator.Element) throws -> Bool) rethrows -> [Self.SubSequence]
How does the following implementation work with above declaration?
someString.characters.split { $0 == "." }
SWIFT messages consist of five blocks of data including three headers, message content, and a trailer. Message types are crucial to identifying content. All SWIFT messages include the literal "MT" (message type/text). This is followed by a three-digit number that denotes the message category, group and type.
Logical Terminal (LT) Address (Block 1) The logical terminal address of the sender for messages sent or the receiver for messages received from the SWIFT network.
A free-format field in the optional user header of FIN messages. It enables senders to add information of up to 16 characters. There is currently no content classified with this term.
Let's break it down:
public func split(maxSplit: Int = default, allowEmptySlices: Bool = default, @noescape isSeparator: (Self.Generator.Element) throws -> Bool) rethrows -> [Self.SubSequence]
maxSplit
: The first parameter, maxSplit
, allows you to specify the maximum number of pieces that the sequence will be split into. The default is Int.max
.
allowEmptySlices
: The second parameter, allowEmptySlices
specifies whether or not two consecutive separators in the sequence should lead to an empty slice. The default is false
. For example if you had a String, "A..B"
, and you split on the .
character, you could end up with either two (["A", "B"]
) or three (["A", "", "B"]
) items in the output array depending on what you pass for this parameter.
isSeparator
: The last parameter is the closure that you pass to identify where to split the sequence.
Since both maxSplit
and allowEmptySlices
have default arguments, you don't need to include them in your function call unless you want to change them. The only parameter that you have to supply is the isSeparator
closure.
In your case, you called:
someString.characters.split { $0 == "."}
...which is the equivalent of:
someString.characters.split(maxSplit: Int.max, allowEmptySlices: false) { $0 == ".' }
You could also write your function call like this:
someString.characters.split(isSeparator: { $0 == "." })
The way that you have written it makes use of the "trailing closure" syntax. If a function takes a closure as it's final argument, you can move the closure outside the parentheses like this:
someString.characters.split() { $0 == "." }
And if the function takes only one argument (not counting any default arguments that you are not supplying) then you can omit the parentheses altogether:
someString.characters.split { $0 == "." }
At the highest level, what happens is that split
iterates through the sequence of characters. It tests each character using the supplied closure, and if the closure returns true
, it splits the sequence on that character. In your case it will split the sequence of characters every time it locates a "."
.
Some other notes:
rethrows
: The whole function is marked rethrows
. It will throw an error, but only if the closure that you pass for the isSeparator
argument throws an error itself. Note that the isSeparator
parameter allows you to pass a closure that throws an error, but you don't have to. Any time a function accepts a closure that throws an error, it will also accept a closure that does not throw. This is because non-throwing functions are a sub-type of throwing functions.
@noescape
: The isSeparator
parameter is marked @noescape
. That simply means that nothing in the closure will survive past the end of the call to split
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With