K. Lundberg klundberg

New Build System Tricks

Command Line

alias xcbuild=$(xcode-select -p)/../SharedFrameworks/XCBuild.framework/Versions/A/Support/xcbuild
# THIS DOESNT WORK YET: xcbuild openIDEConsole  # … then switch to Xcode ➡️
xcbuild showSpecs
xcbuild build <foo.pif> [—target <target>]

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

Core Priorities

Briefly state your (2-5) core priorities that represent your primary areas of focus and the targeted business impact. Also include your critical indicators of success for each

Lower the barrier of entry to adopting and understanding TypeScript. Will validate by re-requesting feedback from the community a second time like issues #31983 and hopefully it should be a new set of problems.
Understand the TypeScript Codebase enough to provide useful API documentation and fix bugs. Validated by having a more comprehensive set of tools for understanding
Make contributing to TypeScript easier, and reduce the amount of work maintainers need to do. Validated probably by the number of open PRs, and the number of external contributors per release.

	import Foundation

	@dynamicMemberLookup
	enum JSON: Codable, CustomStringConvertible {
	var description: String {
	switch self {
	case .string(let string): return "\"\(string)\""
	case .number(let double):
	if let int = Int(exactly: double) {
	return "\(int)"

	import requests
	import json
	import itertools
	import time

	start_time = time.time()

	def get_hash(patches):
	seek = '1573395'
	for patch in patches:

	public struct AnyCodable: Codable {
	public let value: Any?

	public init(_ value: Any?) {
	self.value = value
	}

	public init(from decoder: Decoder) throws {
	let container = try decoder.singleValueContainer()

	struct AnyCodingKey: CodingKey {
	var stringValue: String
	var intValue: Int?

	init?(intValue: Int) {
	self.intValue = intValue
	self.stringValue = "\(intValue)"
	}
	init?(stringValue: String) {
	self.intValue = nil

	import Foundation

	class DictionaryDecoder {
	init() { }

	func decode<T: Decodable>(_ type: T.Type, from data: [String: Any]) throws -> T {
	let decoder = _Decoder(codingPath: [], source: data)
	return try T(from: decoder)
	}
	}

	@propertyWrapper
	public struct AnyProxy<EnclosingSelf, Value> {
	private let keyPath: ReferenceWritableKeyPath<EnclosingSelf, Value>

	public init(_ keyPath: ReferenceWritableKeyPath<EnclosingSelf, Value>) {
	self.keyPath = keyPath
	}

	@available(*, unavailable, message: "The wrapped value must be accessed from the enclosing instance property.")
	public var wrappedValue: Value {

	import Foundation

	public protocol DefaultValue {
	associatedtype Value: Codable

	static var value: Value { get }
	}

	@propertyWrapper
	public struct Default<Default: DefaultValue>: Codable {