Skip to content

Update compiler guards for concurrency #1277

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

Merged
merged 1 commit into from
Sep 27, 2021

Conversation

glbrntt
Copy link
Collaborator

@glbrntt glbrntt commented Sep 27, 2021

Motivation:

The 'right' way to check if Swift concurrency is available is to use
#if compiler(>=5.5) && canImport(_Concurrency). We are missing
currently missing the canImport check.

Modifications:

Add check for canImport(_Concurrency).

Results:

We more correctly check whether concurrency is available.

Motivation:

The 'right' way to check if Swift concurrency is available is to use
`#if compiler(>=5.5) && canImport(_Concurrency)`. We are missing
currently missing the `canImport` check.

Modifications:

Add check for `canImport(_Concurrency)`.

Results:

We more correctly check whether concurrency is available.
@glbrntt glbrntt added the 🔨 semver/patch No public API change. label Sep 27, 2021
@glbrntt glbrntt requested a review from fabianfett September 27, 2021 14:41
@Lukasa Lukasa merged commit 1072237 into grpc:1.4.1-async-await Sep 27, 2021
@glbrntt glbrntt deleted the gb-update-compiler-guard branch September 27, 2021 15:33
glbrntt added a commit that referenced this pull request Nov 26, 2021
Motivation:

The 'right' way to check if Swift concurrency is available is to use
`#if compiler(>=5.5) && canImport(_Concurrency)`. We are missing
currently missing the `canImport` check.

Modifications:

Add check for `canImport(_Concurrency)`.

Results:

We more correctly check whether concurrency is available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants