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

Migrate to Xcode 16 minimum #883

Draft
wants to merge 38 commits into
base: v.next
Choose a base branch
from
Draft

Migrate to Xcode 16 minimum #883

wants to merge 38 commits into from

Conversation

dfeinzimer
Copy link
Collaborator

@dfeinzimer dfeinzimer commented Sep 20, 2024

✅ Verified all example projects build okay
✅ Verified tests
✅ Verified affected component behavior

To Do:

  • Further investigate Tabletop AR crash

@dfeinzimer dfeinzimer self-assigned this Sep 20, 2024
…int:with:)`

Fixes error: Main actor-isolated value of type '() async -> Void' passed as a strongly transferred parameter; later accesses could race
…erform:)`

Fixes error: Main actor-isolated property 'microphoneAccessAlertIsVisible' can not be mutated from a Sendable closure
…erform:)`

Fixes error: Assigning non-sendable parameter 'action' to a @sendable closure
Main actor-isolated value of type '() async throws -> ()' passed as a strongly transferred parameter; later accesses could race
Main actor-isolated value of type '() async throws -> ()' passed as a strongly transferred parameter; later accesses could race
Main actor-isolated value of type '() async -> ()' passed as a strongly transferred parameter; later accesses could race
Main actor-isolated value of type '() async -> ()' passed as a strongly transferred parameter; later accesses could race
Property was unused and Main actor-isolated property 'id' cannot be used to satisfy nonisolated protocol requirement
Fixes various instances of "Call to main actor-isolated initializer 'init()' in a synchronous nonisolated context" in Examples.swift
Fixes "Sending 'self' risks causing data races" @ ARSwiftUIView.swift line 153
Sending 'value' risks causing data races
@@ -15,7 +15,7 @@
import ArcGIS

/// Defines the contract for a search result provider.
public protocol SearchSource {
public protocol SearchSource: Sendable {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While adopting the Sendable protocol is easy, doing so right can be hard. Neither of the conforming types are actually sendable nor would it be easy to make them so. That is why I didn't do this myself when enabling complete strict concurrency. We may end up having no other choice, but if so, we should make an effort to make the conforming types thread safe, as difficult as that will be. The best option is probably to re-design the API, but I don't think we want to do that right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants