Manuel Maly manmal

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

	//: Playground - noun: a place where people can play
	import UIKit

	private class Weak: Hashable {
	let hashValue: Int
	weak var value: AnyObject?

	init(value: AnyObject) {
	self.value = value
	self.hashValue = ObjectIdentifier(value).hashValue

	import UIKit

	class PushedViewController: UIViewController {

	var currentWeather: Observable<Double>!
	private let disposeBag = MyDisposeBag()

	override func viewDidLoad() {
	super.viewDidLoad()

	enum JSON: Decodable {
	case bool(Bool)
	case double(Double)
	case string(String)
	indirect case array([JSON])
	indirect case dictionary([String: JSON])

	init(from decoder: Decoder) throws {
	if let container = try? decoder.container(keyedBy: JSONCodingKeys.self) {
	self = JSON(from: container)

	//
	// Alamofire+Reactive.swift
	// architecture
	//
	// Created by MakotoAoyama on 9/8/17.
	//

	import Foundation
	import ReactiveSwift
	import Alamofire

	protocol FRCCollectionViewDelegate: class {
	func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell
	}

	class FRCCollectionViewDataSource<FetchRequestResult: NSFetchRequestResult>: NSObject, UICollectionViewDataSource, NSFetchedResultsControllerDelegate {

	let frc: NSFetchedResultsController<FetchRequestResult>
	weak var collectionView: UICollectionView?
	weak var delegate: FRCCollectionViewDelegate?

	final class Loader: BindableObject {
	let didChange = PassthroughSubject<Data?, Never>()
	var task: URLSessionDataTask!
	var data: Data? = nil {
	didSet {
	didChange.send(data)
	}
	}

	init(_ url: URL) {

	@DynamicColor(lightVariant: .black, darkVariant: .white)
	static var dynamicLabelColor: UIColor

	@propertyWrapper
	struct DynamicColor {
	let lightVariant: UIColor
	let darkVariant: UIColor

	var wrappedValue: UIColor {
	get {

	// Authoer: The SwiftUI Lab
	// Full article: https://swiftui-lab.com/scrollview-pull-to-refresh/

	import SwiftUI

	struct RefreshableScrollView<Content: View>: View {
	@State private var previousScrollOffset: CGFloat = 0
	@State private var scrollOffset: CGFloat = 0
	@State private var frozen: Bool = false
	@State private var rotation: Angle = .degrees(0)

	/// Used to identify traits of the current UI Environment - especially useful for cross-platform code
	public struct MNCUITraits: Withable {

	/// Does not identify the device type, but the idiom of the layout to apply
	/// This means that e.g. on iPad the layoutIdiom can be `.phone`, if run in Split Screen or SlideOver
	public enum LayoutIdiom {
	case phone(hasRoundCorners: Bool)
	case pad(hasRoundCorners: Bool)
	case mac
	}