Updated with info from https://developer.apple.com/documentation/testing fetched via Firecrawl on June 7, 2025.
A hands-on, comprehensive guide for migrating from XCTest to Swift Testing and mastering the new framework. This playbook integrates the latest patterns and best practices from WWDC 2024 and official Apple documentation to make your tests more powerful, expressive, and maintainable.
Ensure your environment is set up for a smooth, gradual migration.
| import { | |
| Operation, | |
| Resource, | |
| Context, | |
| action, | |
| resource, | |
| spawn, | |
| sleep, | |
| main, | |
| suspend as effectionSuspend, |
The Model Context Protocol (MCP) represents a fundamental shift in how AI applications connect to external systems. Introduced by Anthropic in November 2024, MCP chose a client-server architecture over alternatives like peer-to-peer or monolithic designs to solve the "M×N problem" - where M AI applications need to integrate with N data sources, traditionally requiring M×N custom integrations. The client-server model transforms this into an M+N solution through standardized, secure, and scalable connections.
This architectural decision reflects deep technical considerations: security isolation between components, modular extensibility for diverse integrations, and protocol standardization that enables any MCP client to work with any MCP server regardless of implementation language or platform. The design philosophy prioritizes developer simplicity while maintaining enterprise-grade security boundaries - what Anthropic calls "
| // Deep Dive: Prompts as Delimited Continuations in TypeScript | |
| // ============================================================================= | |
| // 1. PROMPTS AS INITIAL CONTINUATIONS | |
| // ============================================================================= | |
| /** | |
| * Prompts as Initial Continuations treats the prompt itself as the starting | |
| * continuation that establishes the computational context. The prompt becomes | |
| * a first-class continuation that can be captured, modified, and resumed. |
| // A2A Protocol Implementation Example in Swift using Hummingbird | |
| // | |
| // This is a Swift implementation of Google's Agent-to-Agent (A2A) protocol using Hummingbird 2. | |
| // The example demonstrates two components: | |
| // 1. An A2A Server: An agent that exposes an HTTP endpoint implementing A2A protocol methods | |
| // 2. An A2A Client: An application that consumes A2A services | |
| import Foundation | |
| import Hummingbird | |
| import NIOCore |
| import streamlit as st | |
| import concurrent.futures # We'll do computations in separate processes! | |
| import mymodule # This is where you'll do the computation | |
| # Your st calls must go inside this IF block. | |
| if __name__ == '__main__': | |
| st.write("Starting a long computation on another process") | |
| # Pick max number of concurrent processes. Depends on how heavy your computation is, and how | |
| # powerful your machine is. |
Just chat.deepseek.com with prompts adapted from this gist.
qX_0 variants, they are actually quite straight-forward so deepseek can come up with a correct result in 1 shot.qX_K it's more complicated, I would say most of the time I need to re-prompt it 4 to 8 more times.q6_K, the code never works until I ask it to only optimize one specific part, while leaving the rest intact (so it does not mess up everything)
| // Backports the Swift 6 type Mutex<Value> to Swift 5 and all Darwin platforms via OSAllocatedUnfairLock. | |
| // Lightweight version of https://github.com/swhitty/swift-mutex | |
| // Feel free to use any part of this gist. | |
| // Note: ~Copyable are not supported | |
| #if compiler(>=6) | |
| @available(iOS, introduced: 16.0, deprecated: 18.0, message: "use Mutex from Synchronization module included with Swift 6") | |
| @available(macOS, introduced: 13.0, deprecated: 15.0, message: "use Mutex from Synchronization module included with Swift 6") | |
| public struct Mutex<Value>: @unchecked Sendable { |
| import os.lock | |
| /// `CancellingContinuation` is built on top of `CheckedContinuation` and | |
| /// provides some additional features. It can be used as a drop-in replacement, | |
| /// providing a similar API. | |
| /// | |
| /// ## Automatic cancellation | |
| /// When the suspended task is cancelled the continuation is automatically | |
| /// resumed with a `CancellationError`. After that, normally resuming the | |
| /// continuation from client is silently ignored. |