Author: Chris Lattner
// Created by Caleb Davenport on 7/14/17. | |
import UIKit | |
final class ActionSheetPresentationController: UIPresentationController { | |
// MARK: - Properties | |
private var dimmingView: UIView! |
- Proposal: SE-XXXX
- Authors: Chris Lattner, Joe Groff
Modern Cocoa development involves a lot of asynchronous programming using closures and completion handlers, but these APIs are hard to use. This gets particularly problematic when many asynchronous operations are used, error handling is required, or control flow between asynchronous calls gets complicated. This proposal describes a language extension to make this a lot more natural and less error prone.
This paper introduces a first class Coroutine model to Swift. Functions can opt into to being async, allowing the programmer to compose complex logic involving asynchronous operations, leaving the compiler in charge of producing the necessary closures and state machines to implement that logic.
This is a curated list of iOS (Swift & ObjC) frameworks which are inspired by React and Elm.
- ReactSwift by @ColinEberhardt
- https://github.com/ColinEberhardt/ReactSwift
// clang -cc1 -analyzer-checker-help | |
// OVERVIEW: Clang Static Analyzer Checkers List | |
// USAGE: -analyzer-checker <CHECKER or PACKAGE,...> | |
// | |
// CHECKERS: | |
// alpha.core.BoolAssignment Warn about assigning non-{0,1} values to Boolean variables | |
// alpha.core.CallAndMessageUnInitRefArg | |
// Check for logical errors for function calls and Objective-C message expressions (e.g., uninitialized arguments, null function pointers, and pointer to undefined variables) | |
// alpha.core.CastSize Check when casting a malloc'ed type T, whether the size is a multiple of the size of T | |
// alpha.core.CastToStruct Check for cast from non-struct pointer to struct pointer |
//===----------------------------------------------------------------------===// | |
//===--- Defining Collections, easy as Pie --------------------------------===// | |
//===----------------------------------------------------------------------===// | |
struct Digits : PieCollection { | |
let startState: Optional = 0 | |
func iterate(from state: Int) -> (nextState: Int?, element: Int) { | |
return (nextState: state+1 < 10 ? state+1 : nil, element: state) | |
} | |
} |
protocol TextContaining { | |
var isEmpty: Bool { get } | |
} | |
extension String: TextContaining { | |
} | |
extension Optional where Wrapped: TextContaining { | |
var isEmpty: Bool { | |
switch self { |
// gem install cocoapods-playgrounds | |
// pod playgrounds LibYAML | |
// Update: @floriankugler had a great idea to use UnsafeBufferPointer | |
// Paste in the following: | |
import LibYAML | |
public struct YAMLError: ErrorType { |
A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.
With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.
We use GraphQL to dyn
final class CenteringView: UIView { | |
// MARK: - Initialization | |
init(contentView: UIView) { | |
super.init(frame: .zero) | |
addSubview(contentView) | |
contentView.translatesAutoresizingMaskIntoConstraints = false | |
NSLayoutConstraint.activateConstraints([ |