IanKeen

import Foundation

public protocol CodingStrategy {
    associatedtype Converted
    associatedtype RawValue: Codable

    static func toRaw(_ value: Converted) throws -> RawValue
    static func toValue(_ raw: RawValue) throws -> Converted
}

anandabits

/// - returns: `true` when dynamic type is `Equatable` and `==` returns `true`, otherwise `false`.
func areEquatablyEqual(_ lhs: Any, _ rhs: Any) -> Bool {
    func receiveLHS<LHS>(_ typedLHS: LHS) -> Bool {
        guard
            let rhsAsLHS = rhs as? LHS
            else { return false }
        return areEquatablyEqual(typedLHS, rhsAsLHS)
    }
    return _openExistential(lhs, do: receiveLHS)
}

IanKeen

@dynamicMemberLookup
struct Combined<A, B> {
    private let a: A
    private let b: B

    init(a: A, b: B) { (self.a, self.b) = (a, b) }

    subscript<T>(dynamicMember keyPath: KeyPath<A, T>) -> T {
        return a[keyPath: keyPath]
    }

IanKeen

class DictionaryEncoder {
    init() { }
    
    func encode(_ value: Encodable) throws -> [String: Any] {
        let encoder = _Encoder(codingPath: [])
        try value.encode(to: encoder)
        
        guard let result = encoder.value as? [String: Any] else {
            throw EncodingError.invalidValue(encoder.value as Any, .init(codingPath: [], debugDescription: "Invalid root container"))
        }

IanKeen

protocol AutoObjectiveCBridgeable: _ObjectiveCBridgeable where _ObjectiveCType == ObjcType {
    associatedtype ObjcType
    
    func toObjectiveC() -> ObjcType
    static func fromObjectiveC(_ instance: ObjcType) -> Self
}

extension AutoObjectiveCBridgeable {
    // MARK: - _ObjectiveCBridgeable
    func _bridgeToObjectiveC() -> ObjcType {

chriseidhof

import Foundation
import NIO
import NIOHTTP1

// Inspired/parts copied from http://www.alwaysrightinstitute.com/microexpress-nio/

final class HelloHandler: ChannelInboundHandler {
    typealias InboundIn = HTTPServerRequestPart
    
    func channelRead(ctx: ChannelHandlerContext, data: NIOAny) {

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

khanlou

struct SortedArray<Element, ComparableProperty: Comparable> {

    let propertyAccessor: (Element) -> ComparableProperty

    private var elements: [Element]

    public init(propertyAccessor: @escaping (Element) -> ComparableProperty) {
        self.elements = []
        self.propertyAccessor = propertyAccessor
    }

maelvls

How to automate the build of bottles on your Homebrew tap

Note on Oct 4, 2018: due to a change in Homebrew's brew test-bot behaviour, the user must set HOMEBREW_TRAVIS_CI and HOMEBREW_TRAVIS_SUDO appropriately (it was previously using Travis-CI-provided TRAVIS and TRAVIS_SUDO).

This tutorial is a follow-up to the discussion we had on davidchall/homebrew-hep#114. It relies on a fork of the test-bot provided by davidchall; you can get it with brew tap maelvalais/test-bot. First:

1. the Github project must be of the form https://github.com//homebrew- with the following tree

ericclemmons

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here