Releases: RougeWare/Swift-Special-String
Releases · RougeWare/Swift-Special-String
1.2 • Explicit Swift Concurrency support!
Now, if your special string's special type is Sendable
, then so is your special string!
Patch changes
1.2.0
• #8: Added passthrough support forSendable
1.1.3 - `EssentiallyAString` (and therefore `SpecialString`) now conforms to `Codable`
Now, both EssentiallyAString
and SpecialString
conform to Codable
, making it easy to encode and decode your special string, or anything else which is essentially just a string
Patch Changes
- 1.1.3
- Added a dynamic library product whose name is a valid bundle identifier
- Deprecated previous dynamic library product because its name caused problems when submitting to the App Store
- 1.1.2
- Added alternative dynamic library product
- 1.1.1
- Added dual licenses
1.0.0 - MVP
SpecialString
- Leverage Swift's powerful type system to make sure no two kinds of string are mixed upEssentiallyAString
- The backbone of the handy ergonomics ofSpecialString
- Premade special strings
UnsafeUserInput
- Unsafe user input. It must be sanitized before it can be safely used.SanitizedUserInput
- User input which has gone through some process and can now be deemed safe to use.Password
- A password. It must never be serialized as a plaintext string.