Last active
May 8, 2021 10:54
-
-
Save nicklockwood/81b9f122f3db9e7132be7bd61d0c0cea to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
extension Data { | |
init?(hexString: String) { | |
let count = hexString.count / 2 | |
var data = Data(capacity: count) | |
var i = hexString.startIndex | |
for _ in 0 ..< count { | |
let j = hexString.index(after: i) | |
if var byte = UInt8(hexString[i ... j], radix: 16) { | |
data.append(&byte, count: 1) | |
} else { | |
return nil | |
} | |
i = hexString.index(after: j) | |
} | |
self = data | |
} | |
} |
That works and shows me hexDigitValue which I should have used in the iterator approach. Is there any advantage to the Substring over the iterator? I imagine it just has an additional end index though I haven’t checked.
Also if we use iterator it can be made generic over collections of Characters so it should work on Strings, Substrings and arrays of characters. It could work on Sequences if we didn’t need the count upfront.
extension Data {
init?<S>(hexString: S) where S : Collection, S.Element == Character {
let count = hexString.count / 2
var data = Data(capacity: count)
var itr = hexString.makeIterator()
for _ in 0 ..< count {
guard let hi = itr.next()?.hexDigitValue,
let lo = itr.next()?.hexDigitValue else { return nil }
data.append(UInt8(hi << 4 | lo))
}
self = data
}
}
From my own timings, popping a substring is slower than using index.after(). Not sure how it compares to iterator: https://twitter.com/nicklockwood/status/1382142248247308292
Try using hexString.utf8.withContiguousStorageIfAvailable
. You'll have to write your own hexDigitValue
though.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
embrace your inner
Substring