chriseidhof

// This accompanies http://chris.eidhof.nl/posts/repmin-in-swift.html

import UIKit

// Unfortunately, we need Box

public class Box<T> {
    public let unbox: T
    public init(_ value: T) { self.unbox = value }
}

kongtomorrow

func myAnd(lhs : Bool, rhs : @auto_closure () -> Bool) -> Bool {
    if lhs {
        return rhs()
    } else {
        return false
    }
}

func logAndBool(val : Bool) -> Bool {
    println("evaluating and returning \(val)!")

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

mattt

Greetings, NSHipsters!

As we prepare to increment our NSDateComponents -year by 1, it's time once again for NSHipster end-of-the-year Reader Submissions! Last year, we got some mind-blowing tips and tricks. With the release of iOS 7 & Mavericks, and a year's worth of new developments in the Objective-C ecosystem, there should be a ton of new stuff to write up for this year.

Submit your favorite piece of Objective-C trivia, framework arcana, hidden Xcode feature, or anything else you think is cool, and you could have it featured in the year-end blowout article. Just comment on this gist below!

Here are a few examples of the kind of things I'd like to see:

• Using NSStringFromSelector(@selector()) as a safer way to do KVC / KVO / NSCoding.
• Panic's [rather surprising discovery about the internals of the Lightning Digital AV Adapter](http://www.panic.com/blog/the-lightning-di