Skip to content

[Frontend] Diagnose rather than exit/assert on experimental features #70672

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

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

bnbarham
Copy link
Contributor

@bnbarham bnbarham commented Jan 2, 2024

Diagnose rather than exit when using experimental features that cannot be enabled in production. Also diagnose if using a compiler without SwiftCompilerSources when enabling embedded.

This is especially important for long-running services like sourcekitd, which shouldn't exit just because an invalid argument was passed.

Resolves rdar://119724074.

Diagnose rather than exit when using experimental features that cannot
be enabled in production. Also diagnose if using a compiler without
`SwiftCompilerSources` when enabling embedded.

This is especially important for long-running services like sourcekitd,
which shouldn't exit just because an invalid argument was passed.

Resolves rdar://119724074.
@bnbarham
Copy link
Contributor Author

bnbarham commented Jan 2, 2024

@swift-ci please test

@bnbarham
Copy link
Contributor Author

bnbarham commented Jan 3, 2024

@swift-ci please test Windows platform

@bnbarham bnbarham merged commit 29fdb62 into swiftlang:main Jan 3, 2024
@bnbarham bnbarham deleted the error-not-exit branch January 3, 2024 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants