willmcgugan

Stopwatch {
    layout: horizontal;
    background: $panel-darken-1;
    height: 5;
    min-width: 50;
    margin: 1;
    padding: 1;
}

TimeDisplay {

tgrapperon

import SwiftUI

public extension View {
  func juxtapose<Content>(
    edge: Edge = .top,
    spacing: CGFloat = 8,
    @ViewBuilder content: @escaping () -> Content
  ) -> some View where Content: View {
    modifier(
      JuxtaposedViewModifier(

krzysztofzablocki

import ComposableArchitecture
import Difference
import Foundation

/// A container for storing action filters.
///
/// The logic behind having this rather than a normal closure is that it allows us to namespace and gather action filters together in a consistent manner.
/// - Note: You should be adding extensions in your modules and exposing common filters you might want to use to focus your debugging work, e.g.
/// ```swift
/// extension ActionFilter where Action == AppAction {

ytyubox

extension Result {
    func tryMap<T>(_ transform:(Success) throws -> T)  -> Result<T, Swift.Error> {
        switch self {
            case let .success(success):
                do {
                    return .success(try transform(success))
                } catch {
                    return .failure(error)
                }
            case let .failure(failure):

chriseidhof

// Run any SwiftUI view as a Mac app.

import Cocoa
import SwiftUI

NSApplication.shared.run {
    VStack {
        Text("Hello, World")
        	.padding()
            .background(Capsule().fill(Color.blue))

chriseidhof

import SwiftUI

struct SizeKey: PreferenceKey {
    static func reduce(value: inout CGSize?, nextValue: () -> CGSize?) {
        value = value ?? nextValue()
    }
}
struct ContentView: View {
    @State var width: CGFloat? = nil
    var body: some View {

chriseidhof

//
//  ContentView.swift
//  DeleteMe
//
//  Created by Chris Eidhof on 02.02.21.
//

import SwiftUI

/*

morishin

andymatuschak

A composable pattern for pure state machines with effects

State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?

There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.

Here I present a composable pattern for pure state machiness with effects,

mobilemind

# delete local tag '12345'
git tag -d 12345
# delete remote tag '12345' (eg, GitHub version too)
git push origin :refs/tags/12345
# alternative approach
git push --delete origin tagName
git tag -d tagName