nathantannar4

//
// Copyright (c) Nathan Tannar
//

import SwiftUI
import Engine // https://github.com/nathantannar4/Engine
import Turbocharger // https://github.com/nathantannar4/Turbocharger
import Transmission // https://github.com/nathantannar4/Transmission

#if os(iOS)

ccwasden

// -- Usage

struct Content: View {
    @State var open = false
    @State var popoverSize = CGSize(width: 300, height: 300)
    
    var body: some View {
        WithPopover(
            showPopover: $open,
            popoverSize: popoverSize,

nicklockwood

import Foundation

enum FooType: String, Codable {
  case bar, baz
}

protocol Foo: Codable {
  var type: FooType { get }
}

soffes

CFRunLoopSource is cool. It lets you build behavior similar to the mechanisms that drive setNeedsLayout and setNeedsDisplay in UIKit.

I found myself in need of something like this a couple of times. It's great to know that no matter how many times I say I need to update something, I will get a single callback at the end of the run loop that gives me a chance to perform my work.

Here is a little Swift wrapper that makes the API easier to deal with.

---

Updated for Swift 4

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

smileyborg

// UICollectionView Objective-C example

- (void)viewWillAppear:(BOOL)animated {
    [super viewWillAppear:animated];
        
    NSIndexPath *selectedIndexPath = [[self.collectionView indexPathsForSelectedItems] firstObject];
    if (selectedIndexPath != nil) {
        id<UIViewControllerTransitionCoordinator> coordinator = self.transitionCoordinator;
        if (coordinator != nil) {
            [coordinator animateAlongsideTransition:^(id<UIViewControllerTransitionCoordinatorContext> context) {

gonzalezreal

/// A type that has an "empty" representation.
public protocol EmptyRepresentable {
  static func empty() -> Self
}

extension Array: EmptyRepresentable {
  public static func empty() -> Array<Element> {
    return Array()
  }
}

victorpimentel

@import OCHamcrest;

NS_ASSUME_NONNULL_BEGIN

@interface HCArgumentCaptor (OCMockitoBridge)

- (NSObject *)tm_objectValue;

@end

elm4ward

// ------------------------------------
// Network
// ------------------------------------

struct MeetupResponse {
  var groupName: String = ""
  var groupOrganizers: [String] = []
  var meetupTitle: String = ""
  var meetupAttendes: Int = 0

sjoerdvisscher

struct MinimalDecoder : Decoder {
  var codingPath = [CodingKey?]()
  var userInfo = [CodingUserInfoKey : Any]()
  
  public func container<Key>(keyedBy type: Key.Type) throws -> KeyedDecodingContainer<Key> {
    return KeyedDecodingContainer(MinimalKeyedDecodingContainer<Key>(decoder: self))
  }
  
  public func unkeyedContainer() throws -> UnkeyedDecodingContainer {
    return DecodingContainer(decoder: self)