alongotv

struct ViewControllerLifecycleHandler: UIViewControllerRepresentable {
    func makeCoordinator() -> ViewControllerLifecycleHandler.Coordinator {
        Coordinator(onDidAppear: onDidAppear)
    }

    let onDidAppear: () -> Void
    
    func makeUIViewController(context: UIViewControllerRepresentableContext<ViewControllerLifecycleHandler>) -> UIViewController {
        context.coordinator
    }

dsabanin

defaults write com.apple.dt.Xcode ShowDVTDebugMenu -bool YES
sudo mkdir -p /Applications/Xcode.app/Contents/Developer/AppleInternal/Library/Xcode
sudo touch /Applications/Xcode.app/Contents/Developer/AppleInternal/Library/Xcode/AppleInternal.plist

# Don't forget to restart Xcode

tclementdev

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

• You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.

• Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse

lsavino

DEPRECATED for Xcode 10 🎈

(check out What's New in Swift at 11:40, slide 42)

Whole Module Compilation Optimizations: Why these terms are sometimes misleading

When you look up how to compile swift faster for debug builds, people very earnestly give advice that seems contradictory: you should "try using the whole module optimization flag," and also "never use whole module optimization for debugging". [^1]

This is confusing because some of us are using these two general words:

compilation: "turning text into an executable program"

artemnovichkov

func +=<T>(lhs: inout T?, rhs: T) where T: SignedNumeric {
    switch lhs {
    case .none:
        break
    case .some(let value):
        lhs = .some(value + rhs)
    }
}

func -=<T>(lhs: inout T?, rhs: T) where T: SignedNumeric {

artemnovichkov

//Inspired by: http://merowing.info/2017/04/using-protocol-compositon-for-dependency-injection/

//Protocols for objects owning services. Interactors in VIPER, for example.
protocol HasLogService {
    var logService: LogService { get }
}

protocol HasLoginService {
    var loginService: LoginService { get }
}

sooop

import Foundation

class StreamReader {
    let encoding: String.Encoding
    let chunkSize: Int
    let fileHandle: FileHandle
    var buffer: Data
    let delimPattern : Data
    var isAtEOF: Bool = false
    

artemnovichkov

import UIKit

extension UIView {
    
    func round(with radius: CGFloat, corners: UIRectCorner) {
        let roundedPath = UIBezierPath(roundedRect: bounds,
                                       byRoundingCorners: corners,
                                       cornerRadii: CGSize(width: radius, height: radius))
        let maskLayer = CAShapeLayer()
        maskLayer.path = roundedPath.cgPath

dangthaison91

@jamiepinkham
 public extension ObservableType {
    
    func then(closure: () -> Observable<E>?) -> Observable<E> {
        return then(closure() ?? .empty())
    }
    
    func then(@autoclosure(escaping) closure: () -> Observable<E>) -> Observable<E> {
        let next = Observable.deferred {

erica

import UIKit

// Swift rewrite challenge
// Starting point: https://gist.github.com/jkereako/200342b66b5416fd715a#file-scale-and-crop-image-swift

func scaleAndCropImage(
    image: UIImage,
    toSize size: CGSize,
    fitImage: Bool = true
    ) -> UIImage {