Skip to content

Enable experimental prebuilts #3813

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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

finestructure
Copy link
Member

@finestructure finestructure commented May 30, 2025

Unfortunately, we can't benefit from this new flag that uses pre-built SwiftSyntax libraries at the moment.

Due to our dependence on SwiftPM's branch release/6.1, we depend on SwiftSyntax release/6.1, which does not have a prebuilt library and we end up building it ourselves, as before 😞

@finestructure
Copy link
Member Author

I've asked on the forums if prebuilts might become available for release/6.1. If not, that's another reason to try and drop SwiftPM as a dependency.

https://forums.swift.org/t/preview-swift-syntax-prebuilts-for-macros/80202/21

@finestructure
Copy link
Member Author

finestructure commented May 30, 2025

Actually, this might work. We have good reason to fork SwiftPM already - there are two open PRs we need and they're unlikely to be be merged and cherrypicked to release/6.1 anyway:

Especially the latter we need. We are currently not getting Postgres-NIO package updates due to that.

So since we need that fork, we might as well change SwiftPM's dependency on SwiftSyntax to a release version that has a prebuilt instead of the release/6.1 branch. For what we actually use from SwiftPM this will make no difference.

@finestructure finestructure reopened this May 30, 2025
@finestructure finestructure force-pushed the enable-experimental-prebuilts branch from 3da5237 to 02e010f Compare May 30, 2025 11:22
@finestructure
Copy link
Member Author

I'm not sure if this is working at the moment. Not sure if it's still the wrong SwiftSyntax version or something else. We're getting

CleanShot 2025-05-30 at 14 00 52@2x

on this branch here, vs

CleanShot 2025-05-30 at 14 01 18@2x

on main. The release build is ~10% faster, true, but this might just be jitter?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant