StructureSwiftSyntaxBuilder
BackDeployVersionArgument
A single platform/version pair in a @_backDeploy attribute,e.g. iOS 10.1.
struct BackDeployVersionArgumentMembers
Initializers
init(leadingTrivia: Trivia, garbageBeforeAvailabilityVersionRestriction: ExpressibleAsGarbageNodes?, availabilityVersionRestriction: ExpressibleAsAvailabilityVersionRestriction, garbageBetweenAvailabilityVersionRestrictionAndTrailingComma: ExpressibleAsGarbageNodes?, trailingComma: TokenSyntax?)Creates a
BackDeployVersionArgumentusing the provided parameters.
Instance Methods
func buildSyntax(format: Format, leadingTrivia: Trivia?) -> SyntaxConformance to
SyntaxBuildable.func buildSyntaxList(format: Format, leadingTrivia: Trivia?) -> [Syntax]Builds list of
Syntaxs.func createAttributeList() -> AttributeListConformance to
ExpressibleAsAttributeListfunc createBackDeployVersionArgument() -> BackDeployVersionArgumentConformance to
ExpressibleAsBackDeployVersionArgument.func createBackDeployVersionList() -> BackDeployVersionListConformance to
ExpressibleAsBackDeployVersionListfunc createGarbageNodes() -> GarbageNodesConformance to
ExpressibleAsGarbageNodesfunc createPrecedenceGroupAttributeList() -> PrecedenceGroupAttributeListConformance to
ExpressibleAsPrecedenceGroupAttributeListfunc createSpecializeAttributeSpecList() -> SpecializeAttributeSpecListConformance to
ExpressibleAsSpecializeAttributeSpecListfunc createStringLiteralSegments() -> StringLiteralSegmentsConformance to
ExpressibleAsStringLiteralSegmentsfunc createSwitchCaseList() -> SwitchCaseListConformance to
ExpressibleAsSwitchCaseListfunc createSyntaxBuildable() -> SyntaxBuildableBackDeployVersionArgumentmight conform toExpressibleAsSyntaxBuildablevia differentExpressibleAs*paths. Thus, there are multiple default implementations forcreateSyntaxBuildable, some of which perform conversions throughExpressibleAs*protocols. To resolve the ambiguity, provide a fixed implementation that doesn’t perform any conversions.