Skip to content

Audit and reduce excessive experimental Swift feature flags #17

@leogdion

Description

@leogdion

Problem

Package.swift enables 23+ experimental Swift features. Many may not be necessary and could introduce instability or compilation issues.

Impact

  • Increased build complexity
  • Potential compiler bugs or instability
  • Unclear which features are actually used
  • Maintenance burden

Priority

LOW - Code quality improvement

Expected Fix

  1. Audit each experimental feature flag
  2. Identify which features are actually used in the codebase
  3. Remove unused feature flags
  4. Document why each remaining flag is necessary
  5. Consider using more stable alternatives where possible

Current Feature Flags to Review

  • Strict concurrency checking
  • Existential any keyword
  • Typed throws
  • Noncopyable generics
  • Move-only types
  • Variadic generics
  • Plus ~17 others

Files to Update

  • Package.swift
  • Document findings in CLAUDE.md or IMPLEMENTATION_NOTES.md

Related

From PR #6 review feedback: #6 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions