{"id":36187,"date":"2022-06-10T17:02:33","date_gmt":"2022-06-10T21:02:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36187"},"modified":"2022-12-02T16:09:13","modified_gmt":"2022-12-02T21:09:13","slug":"swift-regex","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/06\/10\/swift-regex\/","title":{"rendered":"Swift Regex"},"content":{"rendered":"

Meet Swift Regex<\/a>:<\/p>\n

Learn how you can process strings more effectively when you take advantage of Swift Regex. Come for concise literals but stay for Regex builders — a new, declarative approach to string processing. We’ll also explore the Unicode models in String and share how Swift Regex can make Unicode-correct processing easy.<\/p><\/blockquote>\n\n

I’m really excited about Swift Regex. It should be much more ergonomic than NSRegularExpression<\/code>, which has always been awkward to use, and faster, too, since it can work directly in Swift’s native string encoding.<\/p>\n\n

Also, in theory it should handle Unicode edge cases better. I’ve run into problems where NSRegularExpression<\/code> returns capture ranges that are valid for NSString<\/code> and String.UTF16View<\/code> but which do not exactly map to valid indexes into the String<\/code> itself.<\/p>\n\n

I’d like to see Apple bring Swift Regex to Core Data, too. First, it would be nice to get consistent results (both matching and performance characteristics) by using the same engine throughout an app. Second, regex matching within SQLite queries is currently slow because it converts each database string from UTF-8 to UTF-16 before invoking ICU.<\/p>\n\n

Swift Regex: Beyond the basics<\/a>:<\/p>\n

Go beyond the basics of string processing with Swift Regex. We’ll share an overview of Regex and how it works, explore Foundation’s rich data parsers and discover how to integrate your own, and delve into captures. We’ll also provide best practices for matching strings and wielding Regex-powered algorithms with ease.<\/p><\/blockquote>\n\n

Ron Avitzur<\/a>:<\/p>\n

\n

Tis nifty watching Xcode refactor \/(([0-9]*\\.?[0-9]+)([eE][-+]?[0-9]+)?)|NaN\/<\/code> to a Regex Builder, even if the compiler is unable to type-check this expression in reasonable time.<\/p>\n<\/blockquote>\n\n

Steve Canon<\/a>:<\/p>\n

\n

The converter that Xcode uses for regex -> builder is in the experimental-string-processing repo.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n