Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swift Concurrency & Swift 6 Strict Currency #222

Open
orchetect opened this issue Oct 29, 2024 · 0 comments
Open

Swift Concurrency & Swift 6 Strict Currency #222

orchetect opened this issue Oct 29, 2024 · 0 comments
Assignees
Labels
♻️ in progress Issue is actively being worked on 🎩 refinement An enhancement to an existing feature
Milestone

Comments

@orchetect
Copy link
Owner

Proposal

Refactors are under way for:

  • bringing MIDIKit up to modern Swift Concurrency standards, including compliance with Swift 6's Strict Concurrency mode
  • considerations for the @Observable attribute for objects where appropriate, while maintaining backwards-compatibility as far as possible

Benefits

  • Compatibility with projects adopting Swift 6
  • Improved thread-safety and reliability
  • Better interoperability with SwiftUI

Considerations

Because of the code-breaking nature of the requirements of these refactors, they will not be included until the MIDIKit 1.0.0 release which also requires some outstanding work in other areas.

Note

Swift Concurrency requires the package's minimum platform requirements to be bumped to macOS 10.15, iOS 13, tvOS 13, and watchOS 6.

@orchetect orchetect added ♻️ in progress Issue is actively being worked on 🎩 refinement An enhancement to an existing feature labels Oct 29, 2024
@orchetect orchetect added this to the 0.10.0 milestone Oct 29, 2024
@orchetect orchetect self-assigned this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
♻️ in progress Issue is actively being worked on 🎩 refinement An enhancement to an existing feature
Projects
None yet
Development

No branches or pull requests

1 participant