Adjusting saturation and applying tone mapping

At a glance

Project structure

Source bundle/
├── yCbCrAdjustment/
│   ├── YpCbCrAdjustmentApp.swift
│   ├── ContentView.swift
│   ├── YpCbCrAdjustment.swift
│   ├── Base.lproj/
│   │   └── Main.storyboard
│   ├── Info.plist
│   └── yCbCrAdjustment.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── yCbCrAdjustment.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 6 project/configuration file(s) and 5 source declaration(s).

Overall architecture

flowchart LR
    N1["YpCbCrAdjustmentApp"]
    N2["ContentView"]
    N3["Accelerate APIs"]
    N1 --> N2
    N2 --> N3

Reference code

yCbCrAdjustment/YpCbCrAdjustmentApp.swift:10 — architecture anchor

@main
struct YpCbCrAdjustmentApp: App {

    @StateObject private var yCbCrAdjustment = YpCbCrAdjustment(image: #imageLiteral(resourceName: "Rainbow_1.png"))

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(yCbCrAdjustment)
        }
    }
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Accelerate.

Ownership and state

classDiagram
    YpCbCrAdjustmentApp *-- YpCbCrAdjustment : yCbCrAdjustment
    ContentView o-- YpCbCrAdjustment : ycbcrAdjustment
    ContentView o-- NumberFormatter : formatter
    ContentView o-- Font : font

Ownership evidence

yCbCrAdjustment/YpCbCrAdjustmentApp.swift:13 — stored dependency or nearest verified ownership anchor

@main
struct YpCbCrAdjustmentApp: App {
    // ...
    @StateObject private var yCbCrAdjustment = YpCbCrAdjustment(image: #imageLiteral(resourceName: "Rainbow_1.png"))
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

yCbCrAdjustment/YpCbCrAdjustment.swift:93 — representative execution boundary

import Combine
class YpCbCrAdjustment: ObservableObject {
    // ...
            .receive(on: DispatchQueue.global(qos: .userInteractive))
    // ...
}

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

yCbCrAdjustment/YpCbCrAdjustmentApp.swift:11 — representative type boundary

@main
struct YpCbCrAdjustmentApp: App {
    // ...
    @StateObject private var yCbCrAdjustment = YpCbCrAdjustment(image: #imageLiteral(resourceName: "Rainbow_1.png"))
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

yCbCrAdjustment/YpCbCrAdjustment.swift:47 — representative boundary

    private lazy var argbSource: vImage.PixelBuffer<vImage.Interleaved8x4> = {
        return try! vImage.PixelBuffer<vImage.Interleaved8x4>(cgImage: sourceCGImage,
                                                              cgImageFormat: &format)
    }()

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: YpCbCrAdjustmentApp; View: ContentView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: format, reset, applyAdjustment, applyGammaToLuma, applyLinearToCbCr, applyGammaToCbCr, convert, remap.
• Files: yCbCrAdjustment/YpCbCrAdjustmentApp.swift, yCbCrAdjustment/ContentView.swift, yCbCrAdjustment/YpCbCrAdjustment.swift.

Architecture takeaways

• YpCbCrAdjustmentApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, Accelerate, Cocoa through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation