Releases · RougeWare/Swift-String-Integer-Access

11 Jun 17:10

2.1.0

595374e

Latest

This even introduces some functionality that Swift Strings don't have!

var someString = "Hello, World!"

someString[1...4]           // "ello"
someString[7..<12] = "Mars" // "Hello, Mars!"


someString[orNil: ...4]   = "Howdy"      // "Howdy, Mars!"
someString[orNil: 999...] = "Boundaries" // "Howdy, Mars!"

Licensing

This also changes the license so it's explicitly BH-1-PS.

Assets 2

22 May 19:42

KyNorthstar

2.0.0

57b379e

2.0.0 - SafeStringIntegerAccess

More integer accessors, these without crashes! Drawing from Swift Safe Collection Access, you can now access strings with Ints, and if you pass an invalid value to these new orNil subscripts and functions, they will return nil instead of crashing!

import SafeStringIntegerAccess

let someString = "Hello, World!"

someString[orNil: 3..<5] == "lo"
someString[orNil: 3..<5] == someString[3..<5]
someString[orNil: 42..<99] == nil 
someString[orNil: -10 ..< -5] == nil

To take advantage of this new behavior, import SafeStringIntegerAccess. This will give the old behavior as well. If you just want the old behavior, import StringIntegerAccess instead.

Additionally, the NSRange subscript introduced in 1.2.0 now returns a Substring rather than an Optional<Substring>, crashing if the given range is invalid. For the non-crashing, optional-return behavior, pass your NSRange to the [orNil:] subscript.

In doing this update, the NSRange subscripts were updated to fix a bug with the way it processes strings with higher-plane Unicode characters and grapheme clusters.

Assets 2