joshavant

extension UIView {
    @objc func exerciseAmbiguityInLayoutRepeatedly() {
        if self.hasAmbiguousLayout {
            Timer.scheduledTimer(timeInterval: 0.5,
                                 target: self,
                                 selector: #selector(UIView.exerciseAmbiguityInLayout),
                                 userInfo: nil,
                                 repeats: true)
        }
    }

jessesquires

# blog post
#
# https://www.jessesquires.com/blog/customizing-git-log/

git log --graph --pretty=format:'commit: %C(bold red)%h%Creset %C(red)<%H>%Creset %C(bold magenta)%d %Creset%ndate: %C(bold yellow)%cd %Creset%C(yellow)%cr%Creset%nauthor: %C(bold blue)%an%Creset %C(blue)<%ae>%Creset%n%C(cyan)%s%n%Creset'

steipete

# The trick is to link the DeviceSupport folder from the beta to the stable version.
# sudo needed if you run the Mac App Store version. Always download the dmg instead... you'll thank me later :)

# Support iOS 15 devices (Xcode 13.0) with Xcode 12.5:
sudo ln -s /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.0 /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport

# Then restart Xcode and reconnect your devices. You will need to do that for every beta of future iOS versions

# (A similar approach works for older versions too, just change the version number after DeviceSupport)

alexcurylo

class SomeViewController: UIViewController {
 
    private typealias My = SomeViewController
    
    private let videoPlayer: AVPlayer
    private let videoPlayerLayer: AVPlayerLayer
    
    override init(nibName: String?, bundle nibBundle: NSBundle?) {
        (videoPlayer, videoPlayerLayer) = My.commonInit()
 

nicklockwood

Thoughts on Swift 2 Errors

When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.

So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.

Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?

I'm going to cover three things in this post:

natecook1000

extension NSTimer {
    /**
    Creates and schedules a one-time `NSTimer` instance.
    
    - Parameters:
        - delay: The delay before execution.
        - handler: A closure to execute after `delay`.
    
    - Returns: The newly-created `NSTimer` instance.
    */

calebd

extension Array {
    
    func first() -> Element? {
        if isEmpty {
            return nil
        }
        return self[0]
    }
    
    func last() -> Element? {

odrobnik

- (IBAction)handleTap:(id)sender
{
   BOOL isHiding = !_statusBarHidden;
   _statusBarHidden = isHiding;
   
   [UIView animateWithDuration:UINavigationControllerHideShowBarDuration delay:0 options:0
                    animations:^{
                       [self setNeedsStatusBarAppearanceUpdate];
                    }
                    completion:NULL];

matthiasplappert

@interface UIView (MPAdditions)
@end

@implementation UIView (MPAdditions)

- (id)debugQuickLookObject {
    if (self.bounds.size.width < 0.0f || self.bounds.size.height < 0.0f) {
        return nil;
    }
    

raven

<?xml version="1.0" encoding="UTF-8"?>
<Bucket
   type = "2"
   version = "2.0">
   <Breakpoints>
      <BreakpointProxy
         BreakpointExtensionID = "Xcode.Breakpoint.SymbolicBreakpoint">
         <BreakpointContent
            shouldBeEnabled = "Yes"
            ignoreCount = "0"