erica

import UIKit
import XCPlayground

class ViewController: UIViewController {
    func action() { print("Bing!") }
    
    override func viewDidLoad() {
        super.viewDidLoad()
        view.backgroundColor = .whiteColor()
        

IanKeen

//`UITableViewCell` and `UICollectionViewCell` are `Reusable` by defaut 
//Use the extension method to dequeue an instance of the appropriate `Reusable` 

class MyVC: UITableViewDataSource {
    override func viewDidLoad() {
        super.viewDidLoad()
        tableView
            .registerReusable(FooCell.self)
            .registerReusable(BarCell.self)
    }

mikezs

/**
 * Implemention from here: http://www-igm.univ-mlv.fr/~lecroq/string/node14.html#SECTION00140
 */

extension String {
    private func preBmBc(forString x: String) -> [Character: Int] {
        let m = x.characters.count
        var bmBc = [Character: Int](/*count: alphabetSize, repeatedValue: m*/)
        
        for i in 0...m - 2 {

rnapier

import Foundation

// Why bytesView rather than just extending NSData directly?
// Because this way we can keep our extension internal and not conflict
// with someone who imports us and has also extended NSData.
// If you're top-level code, you can just hoist everyting up to NSData directly.
internal extension NSData {
    var bytesView: BytesView { return BytesView(self) }
}

Kametrixom

protocol ContextError : ErrorType {
	mutating func addContext<T>(type: T.Type)
}

protocol Contextualizable {}
extension Contextualizable {
	func addContext(var error: ContextError) -> ContextError {
		error.addContext(self.dynamicType)
		return error
	}

hectr

// Copyright (c) 2013, Héctor Marqués
//
// Permission to use, copy, modify, and/or distribute this software for any
// purpose with or without fee is hereby granted, provided that the above
// copyright notice and this permission notice appear in all copies.
//
// THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
// REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
// AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
// INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM

Alexander-Ignition

// Asynchronous read

let task = NSURLSession.sharedSession().streamTaskWithHostName("chat.example.com", port: 5555)!
task.resume()

task.readDataOfMinLength(16384, maxLength:65536, timeout: 30.0) {
    (data: NSData?, eof: Bool, error: NSError?) in
    //
}

d-ronnqvist

There was [a tweet][tweetSoto] a couple of days ago that resulted in a discussion/question about what it wrong with the usage of removedOnCompletion = NO in the [SparkRecordingCircle code][code] for that [Subjective-C post][post].

We all kept saying that the explanation doesn't fit in a tweet, so here is my rough explanation about the issues.

But, let me first say that I think that the Subjective-C articles are reallt cool and useful to learn from. This is trying to reason about the general usage of removedOnCompletion = NO, using that code as an example, since that was what was discussed on twitter.

---

The root problem, as [Nacho Soto pointed out][rootProblem], is that removedOnCompletion = NO in combination with fillMode = kCAFillModeForwards is almost always used when you are not updating the model layer. This means that after the animation has finished, what you see on screen is not reflected in the property of the layer. The biggest issue that this can cause is that all the

SteveBenner

#!/usr/bin/env ruby
#
# CLI tool for locating and removing a Homebrew installation
# It replaces the official uninstaller, which is insufficient and often breaks
# If files were removed, the script returns 0; otherwise it returns 1
#
# http://brew.sh/
#
# Copyright (C) 2025 Stephen C. Benner
#

jerrykrinock

#!/usr/bin/perl

=com

PURPOSE

This script will
    Force you through a comprehensive quality-control checklist
    Run Deploymate
    Get the latest version number by reading it from product's Info.plist