krzyzanowskim

extension StringProtocol {
    
    /// str[NSRange(location:0, length: 9)]
    subscript(_ range: NSRange) -> SubSequence {
        guard let stringRange = Range<String.Index>(range, in: self) else {
            fatalError("String index is out of range")
        }
        return self[stringRange]
    }
    

ole

#!/bin/zsh

# Test if the Swift compiler knows about a particular language feature.
#
# Usage:
#
#     swift-has-feature [--swift SWIFT_PATH] [--language-version LANGUAGE_VERSION] FEATURE
#
# The feature should be an upcoming or experimental language feature,
# such as `"StrictConcurrency"` or `"ExistentialAny"`.

krzyzanowskim

extension StringProtocol {
	
	subscript(_ offset: Int) -> String.Element {
		if offset >= 0 {
			self[index(startIndex, offsetBy: offset)]
		} else {
			self[index(endIndex, offsetBy: offset)]			
		}
	}
	

janmazurczak

import Foundation
import Combine

public struct CombineManyLatest<Upstream: Publisher>: Publisher {
    
    public init(_ upstream: Upstream...) {
        self.upstream = upstream
    }
    public init(_ upstream: [Upstream]) {
        self.upstream = upstream

krzyzanowskim

struct ContentView: View {
    @State var color: Color = .Pastel.random()

    var body: some View {
        Rectangle()
            .foregroundColor(color)
            .onTapGesture {
                color = .Pastel.random()
            }
    }

DivineDominion

202207041909 AppStorage extension for strongly typed keys

#appstorage #swiftui

The @AppStorage property wrapper for observable access to UserDefaults keys is stringified.

To get a strongly typed key access, I oriented myself on the @Environment(\.keyPath) wrapper and my experience with SwiftyUserDefaults and its subscript-based access.

// Use defaultValue from the key:
@AppStorage(\.showOnboarding) var showOnboarding

BigZaphod

//
// A Swift property wrapper for adding "indirect" to struct properties.
// Enum supports this out of the box, but for some reason struct doesn't.
//
// This is useful when you want to do something recursive with structs like:
//
// struct Node {
//   var next: Node?
// }
//

theevilbit

#!/bin/zsh

: '
You need a personal access token for GitHub to avoid hitting the rate limit. Refer to the docs:
https://docs.github.com/en/rest/guides/getting-started-with-the-rest-api
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
'

APPLE_OSS_DIR="all_apple_oss_archives"
APPLE_OSS_REPO_FILE="all_apple_oss_repo_names.txt"

krzyzanowskim

// Excerpt from https://github.com/krzyzanowskim/CoreTextWorkshop
// Licence BSD-2 clause
// Marcin Krzyzanowski marcin@krzyzanowskim.com

func getSizeThatFits(_ attributedString: NSAttributedString, maxWidth: CGFloat) -> CGSize {
    let framesetter = CTFramesetterCreateWithAttributedString(attributedString)
    let rectPath = CGRect(origin: .zero, size: CGSize(width: maxWidth, height: 50000))

    let ctFrame = CTFramesetterCreateFrame(framesetter, CFRange(), CGPath(rect: rectPath, transform: nil), nil)

nicklockwood

// This gist demonstrates how you can implement versioning for a Codable struct to support loading
// old serialized data after changing the structure. Notable features of this solution:
//
// * No need to make new properties optional, or to perform post-processing on the struct after
//   loading in ordeer to populate missing values
// * No need to change the call site - from the outside this struct behaves just the same
//   as if we had implemented codable directly in the normal way.
// * Versioning can be applied individually to parents or leaves in a larger tree of
//   structs without affecting the other elements
// * This approach will work even if the original struct was not designed with versioning in mind