Skip to content
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

[SR-1433] [SwiftPM] Enforce manifest strictness #5293

Open
ddunbar opened this issue May 6, 2016 · 0 comments
Open

[SR-1433] [SwiftPM] Enforce manifest strictness #5293

ddunbar opened this issue May 6, 2016 · 0 comments
Labels

Comments

@ddunbar
Copy link
Member

ddunbar commented May 6, 2016

Previous ID SR-1433
Radar None
Original Reporter @ddunbar
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: 5476fbaaa6f239d3f1a53d63fc83392a

Issue Description:

The `Package.swift` file is intended to follow a somewhat rigid file format, and not just be free form Swift code.

In particular, the design goal was that there be a "leading package specifier":

let package = Package(...)

which is Swift code using the PackageDescription APIs, but which can also be mechanically edited. Our intention was to use the Swift AST to parse/type check the code, but then write a new validation pass on the AST to enforce that it followed the conventions which we could mechanically edit.

The hope is that once we had these pieces we could also load the leading package specification from the manifest without needing to execute any code.

We need to implement this latter part of the design, currently we just compile and execute the manifest using the Swift interpreter (which JITs under the covers)

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants