pksunkara

[user]
	name = Pavan Kumar Sunkara
	email = pavan.sss1991@gmail.com
	username = pksunkara
[init]
	defaultBranch = master
[core]
	editor = nvim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	pager = delta

pyrtsa

#import <Foundation/Foundation.h>

@interface NSObject (Cast)
+ (instancetype)cast:(id)object;
@end

@implementation NSObject (Cast)
+ (instancetype)cast:(id)object
{
    return [object isKindOfClass:self] ? object : nil;

AliSoftware

// #!Swift-1.1
import Foundation


// MARK: - (1) classes

// Solution 1:
//  - Use classes instead of struct
// Issue: Violate the concept of moving model to the value layer
//        http://realm.io/news/andy-matuschak-controlling-complexity/

JJediny

There are two types of markup in Liquid: Output and Tag.

• Output markup (which may resolve to text) is surrounded by

{{ matched pairs of curly brackets (ie, braces) }}

• Tag markup (which cannot resolve to text) is surrounded by

aanari

sudo gem uninstall cocoapods
sudo gem install cocoapods -v 1.1.1
rm -rf "${HOME}/Library/Caches/CocoaPods"
rm -rf Pods
pod update

nicklockwood

// Swift's untyped errors are a goddam PiTA. Here's the pattern I use to try to work around this.
// The goal is basically to try to guarantee that every throwing function in the app throws an
// ApplicationError instead of some unknown error type. We can't actually enforce this statically
// But by following this convention we can simplify error handling

enum ApplicationError: Error, CustomStringConvertible {
    
  // These are application-specific errors that may need special treatment
  case specificError1
  case specificError2(SomeType)

Deub27

import UIKit

extension UIStackView {
    
    func removeAllArrangedSubviews() {
        
        let removedSubviews = arrangedSubviews.reduce([]) { (allSubviews, subview) -> [UIView] in
            self.removeArrangedSubview(subview)
            return allSubviews + [subview]
        }

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

woolsweater

import Foundation

/**
 A decodable type that expects its data to be enclosed in a
 keyed container.
 For example, using JSON, a `User` object might be delivered
 inside another object, with `"user"` as the key:
 ```
 { "user" : { "name" : "Alice", "rank" : "Colonel" } }
 ```

davidsteppenbeck

import SwiftUI

enum PreviewProviderMode: CaseIterable {
    
    /// Use for a light appearance preview.
    case lightMode
    
    /// Use for a dark appearance preview.
    case darkMode