[6.0] Parse #if canImport
as a function call instead of a specialized expression node
#2550
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
canImport
inside#if
conditions. This was inconsistent with eg. the parsing of#if swift(<6.0)
, which gets parsed as a function call. To make it easier to interpret the version passed tocanImport(MyModule, _version: <#version#>)
, addExprSyntax.interpretedAsVersionTuple
that takes eg.1.2.3
, which got parsed as a member access3
to the1.2
float literal and re-parses it as aVersionTupleSyntax
. This relaxation also allows string literals as version parameters to#if canImport
.canImport
directives in#if
conditions.CanImportExprSyntax
and it is unlikely that anyone is relying on the interpretation of the version numberCanImportExprSyntax
and provide API to interpret anExprSyntax
as aVersionTupleSyntax
#1972