Skip to content

Using StaticInternalSwiftSyntaxParser? #473

@liamnichols

Description

@liamnichols

👋

I've recently worked on krzysztofzablocki/Sourcery#1037, which took inspiration from realm/SwiftLint#3867 which essentially updates the tools to use StaticInternalSwiftSyntaxParser to make the binaries more portable by removing the dependency on a dylib.

Before taking on any work (since it can get a bit tricky), I wanted to check to see if you'd be keen in taking this direction with Periphery?

Benefits:

  • Portable binary
  • No blockers from building with newer toolchains without having to update SwiftSyntax dependency

Starting with SwiftSyntax for 5.6, the lib_internalSwiftSyntaxParser.dlyb dependency is now a binary dependency in the Package.swift file, which is better than relying on the internal version bundled in Xcode (and linked to that version of Xcode via the rpath), which is a great step in the right direction, but it still has the portability issues described above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions