-
Notifications
You must be signed in to change notification settings - Fork 53
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
fatal compiler error on swift 5.7 and Swift 5.8 #94
Comments
Did you mean version 1.4.x of the plugin? Version 1.0.0 doesn't have the code that's referenced in that log output. Assuming so, you can workaround this error by pinning your swift-docc-plugin dependency to 1.3.0 |
I'm on vacation next week, away from a computer, but I can look at this when I get back if no one else has fixed this by then. |
Yes, I tried with version 1.0.0 and 1.3.0 of the plugin. both generates fatal errors when trying to compile with swift 5.7 or Swift 5.8 |
That makes no sense since the file that those errors are about is 1 day old and the 1.3.0 release is from June 2023 |
Here is the PR where I observed the error. It looks like the latest version is picked up because of the The
This is the error from Jenkins logs for Swift 5.7
This is the error from Jenkins logs for Swift 5.8
I'll force using the 1.3.0 version and report back |
My bad, SPM was picking up the latest version (1.4.1) - I forced the exact 1.3.0 version and this solves the problem. |
Motivation: Building swift-nio-http2 with Swift 5.8 fails due to a compiler error when building swift-docc-plugin (swiftlang/swift-docc-plugin#94). Modifications: - Adjust the dependency version of swift-docc-plugin from `from: "1.0.0"` to `"1.0.0"..<"1.4.0"`. Result: Building swift-nio-http2 with Swift 5.8 will now be successful.
Motivation: Building swift-nio-http2 with Swift 5.8 fails due to a compiler error when building swift-docc-plugin (swiftlang/swift-docc-plugin#94). Modifications: - Adjust the dependency version of swift-docc-plugin from `from: "1.0.0"` to `"1.0.0"..<"1.4.0"`. Result: Building swift-nio-http2 with Swift 5.8 will now be successful.
Motivation: Unfortunately, the DocC plugin no longer builds on 5.8: swiftlang/swift-docc-plugin#94. We need to keep building. Modifications: - Forcefully pin the DocC plugin down. Result: CI works now.
Motivation: Unfortunately, the DocC plugin no longer builds on 5.8: swiftlang/swift-docc-plugin#94. We need to keep building. Modifications: - Forcefully pin the DocC plugin down. Result: CI works now.
I can help fix it. But I think besides it, we need to add some CI check for each PR. Since the Package.swift is 5.6. We need to add a CI to check build success from 5.6 to 6.0 and main.
But sadly GitHub actions are disabled by default in org scope and we need to enable it for this repo or add the CI on ci.swift.org which I do not have permission to contribute.
|
swift-docc-plugin was not building with Swift 5.7 due to using newer syntax which did not exist yet. Fixes the compilation issues to use older Swift syntax. Fixes #94 and rdar://134859979.
@Kyle-Ye Thank you for pinging that, I don't think we want to be supporting as far back as Swift 5.6 -- as part of my fix, I will update Also, +1 on having CI for all the versions we support, to ensure changes are compatible for all. |
Will there be a release soon so projects that had to pin the docc version can unpin? |
Just made a new release for swift-docc-plugin to get the fix out as soon as possible: Pinned projects should now be able to unpin. |
Thank you! |
Description
using Swift Docc plugin 1.0.0, I receive fatal compilation error from Swift on 5.7 and 5.8
or
This breaks our pipeline for The Swift Lambda runtime, see the automated tests for this PR : swift-server/swift-aws-lambda-runtime#342
Checklist
main
branch of this package.Expected Behavior
Should compile on last 3 Swift versions
Actual behavior
Steps To Reproduce
Checkout this PR and compile with a 5.7 or 5.8 toolchain
Swift-DocC Version Information
1.0.0
Swift Compiler Version Information
The text was updated successfully, but these errors were encountered: