{"id":26177,"date":"2019-08-05T16:46:00","date_gmt":"2019-08-05T20:46:00","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=26177"},"modified":"2019-08-05T16:46:00","modified_gmt":"2019-08-05T20:46:00","slug":"phantom-types-in-swift","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/08\/05\/phantom-types-in-swift\/","title":{"rendered":"Phantom Types in Swift"},"content":{"rendered":"

John Sundell<\/a>:<\/p>\n

\n

When converting Data<\/code> into a String<\/code>, like we do above, we pass the encoding that we want the string to be decoded using — in this case UTF8<\/code> — by passing a reference to that type itself. That’s really interesting. If we dive a bit deeper, we can then see that the Swift standard library defines the UTF8<\/code> type that we refer to above as a case-less enum<\/em> within yet another namespace-like<\/em> enum called Unicode<\/code>[…]<\/p>\n

[…]<\/p>\n

Through the use of phantom types, the above two measurement values can’t be mixed, since what kind of unit that each value is for is encoded into that value’s type. That prevents us from accidentally passing a length to a function that accepts an angle, and vice versa — just like how we prevented document formats from being mixed up before.<\/p>\n

[…]<\/p>\n

Using phantom types is an incredibly powerful technique that can let us leverage the type system in order to validate different variants of a given value. While using phantom types usually makes an API more verbose, and does come with the added complexity of generics — when dealing with different formats and variants, it can let us reduce our reliance on run-time checks, and let the compiler perform those checks instead.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n