StructureSwiftSyntaxBuilder
ObjcNamePiece
struct ObjcNamePieceMembers
Initializers
init(leadingTrivia: Trivia, garbageBeforeName: ExpressibleAsGarbageNodes?, name: TokenSyntax, garbageBetweenNameAndDot: ExpressibleAsGarbageNodes?, dot: TokenSyntax?)Creates a
ObjcNamePieceusing the provided parameters.init(leadingTrivia: Trivia, garbageBeforeName: ExpressibleAsGarbageNodes?, name: String, garbageBetweenNameAndDot: ExpressibleAsGarbageNodes?, dot: TokenSyntax?)A convenience initializer that allows:
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 createGarbageNodes() -> GarbageNodesConformance to
ExpressibleAsGarbageNodesfunc createObjcName() -> ObjcNameConformance to
ExpressibleAsObjcNamefunc createObjcNamePiece() -> ObjcNamePieceConformance to
ExpressibleAsObjcNamePiece.func createPrecedenceGroupAttributeList() -> PrecedenceGroupAttributeListConformance to
ExpressibleAsPrecedenceGroupAttributeListfunc createSpecializeAttributeSpecList() -> SpecializeAttributeSpecListConformance to
ExpressibleAsSpecializeAttributeSpecListfunc createStringLiteralSegments() -> StringLiteralSegmentsConformance to
ExpressibleAsStringLiteralSegmentsfunc createSwitchCaseList() -> SwitchCaseListConformance to
ExpressibleAsSwitchCaseListfunc createSyntaxBuildable() -> SyntaxBuildableObjcNamePiecemight 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.