Avi Tsadok
@avitsadok.bsky.social
iOS Developer l Book author | Public speaker
*Raw Identifiers are coming to Swift! (Next Swift version)*
The Swift team has added raw identifiers, making writing more descriptive and natural names for your code easier. Raw identifiers allow names that include spaces, special characters, or even numbers—delimited with backticks (`).
The Swift team has added raw identifiers, making writing more descriptive and natural names for your code easier. Raw identifiers allow names that include spaces, special characters, or even numbers—delimited with backticks (`).
January 2, 2025 at 4:39 AM
*Raw Identifiers are coming to Swift! (Next Swift version)*
The Swift team has added raw identifiers, making writing more descriptive and natural names for your code easier. Raw identifiers allow names that include spaces, special characters, or even numbers—delimited with backticks (`).
The Swift team has added raw identifiers, making writing more descriptive and natural names for your code easier. Raw identifiers allow names that include spaces, special characters, or even numbers—delimited with backticks (`).
December 20, 2024 at 4:57 AM
A nice Swift tip!
When performing string searches, we often write the following:
$0.name.lowercased().contains(searchPhrase.lowercased())
Instead, we can:
$0.name.localizedStandardContains(searchPhrase)
Why is this better?
More Readable, Localization-Friendly, Built-In Case Insensitivity
When performing string searches, we often write the following:
$0.name.lowercased().contains(searchPhrase.lowercased())
Instead, we can:
$0.name.localizedStandardContains(searchPhrase)
Why is this better?
More Readable, Localization-Friendly, Built-In Case Insensitivity
December 17, 2024 at 1:02 PM
A nice Swift tip!
When performing string searches, we often write the following:
$0.name.lowercased().contains(searchPhrase.lowercased())
Instead, we can:
$0.name.localizedStandardContains(searchPhrase)
Why is this better?
More Readable, Localization-Friendly, Built-In Case Insensitivity
When performing string searches, we often write the following:
$0.name.lowercased().contains(searchPhrase.lowercased())
Instead, we can:
$0.name.localizedStandardContains(searchPhrase)
Why is this better?
More Readable, Localization-Friendly, Built-In Case Insensitivity
I am excited to announce that I will be speaking at the iOSkonf conference in North Macedonia!
December 13, 2024 at 11:59 AM
I am excited to announce that I will be speaking at the iOSkonf conference in North Macedonia!