jordansinger

import SwiftUI
import PlaygroundSupport

struct Sunset: View {
    @State var backgroundColor = Color.blue 
    @State var sunSetted = false
    let sunGradient = [Color.yellow, Color.orange]
    let moonGradient = [Color.gray, Color.black]
    @State var alignment = Alignment.top
    

mergesort

import SwiftUI

let colors = [
    Color.pink,
    Color.blue,
    Color.green,
    Color.orange,
    Color.purple,
    Color.black,
]

alemar11

// a.swift
public dynamic func f() {
    print("original")
}

// b.swift
import a

@_dynamicReplacement(for: f())
public func f_b() {

karwa

#! /usr/bin/swift

//
// - This is just some AppKit boilerplate to launch a window.
//
import AppKit
@available(OSX 10.15, *)
class AppDelegate: NSObject, NSApplicationDelegate {
    let window = NSWindow()
    let windowDelegate = WindowDelegate()

artyom-stv

// SwiftUI public API

public protocol View {
    associatedtype Body: View

    var body: Self.Body { get }
}

extension Never: View {
    public typealias Body = Never

AvdLee

find . -type f -name "*.swift" -exec grep -H -c '[^[:space:]]' {} \; | \sort -nr -t":" -k2 | awk -F: '{printf("Your largest file %s contains: %s lines \n", $1, $2); exit;}'

AliSoftware

/*:
 This is a concept re-implementation of the @Binding and @State property wrappers from SwiftUI

 The only purpose of this code is to implement those wrappers myself
   just to understand how they work internally and why they are needed,

 ⚠️ This is not supposed to be a reference implementation nor cover all
      subtleties of the real Binding and State types.
    The only purpose of this playground is to show how re-implementing
      them myself has helped me understand the whole thing better

mxcl

#!/usr/bin/swift sh
import Foundation
import PromiseKit  // @mxcl ~> 6.5
import Swifter     // @mattdonnelly == b27a89

let swifter = Swifter(
    consumerKey: "FILL",
    consumerSecret: "ME",
    oauthToken: "IN",
    oauthTokenSecret: "https://developer.twitter.com/en/docs/basics/apps/overview.html"

bugaevc

// Note: calling fork() can be unsafe and dangerous, that
// is why Swift doesn't let you invoke it directy. Be very
// careful about how you use fork(). For some more details,
// see https://www.evanjones.ca/fork-is-dangerous.html and
// http://www.sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html

import Darwin

let RTLD_DEFAULT = UnsafeMutableRawPointer(bitPattern: -2)
let forkPtr = dlsym(RTLD_DEFAULT, "fork")

GeorgeLyon

Note This is a little out of date. Rust has made some progress on some points, however many points still apply.

Philosophy

Progressive disclosure

Swift shares Rust's enthusiasm for zero-cost abstractions, but also emphasizes progressive disclosure. Progressive disclosure requires that language features should be added in a way that doesn't complicate the rest of the language. This means that Swift aims to be simple for simple tasks, and only as complex as needed for complex tasks.

The compiler works for you