-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[5.5][Serialization] Do not assert when inherited type is null #37476
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
[5.5][Serialization] Do not assert when inherited type is null #37476
Conversation
When compiling with allow errors, it's possible to have invalid inherited types - both null and ErrorType. Cleaned up the tests a little - moved the majority of Frontend/allow-errors.swift into separate files in Serialization/AllowErrors and use split_file.py instead of #defines. Resolves rdar://78048470
@swift-ci please test |
Build failed |
Build failed |
Didn't notice these failed, don't think I got an email with them 🤔. Jobs deleted now so just going to run again. @swift-ci please test |
Build failed |
Build failed |
There was a change in the diagnostics that isn't in 5.5. The error message itself doesn't matter too much here, just that there was one. Simplify the CHECK clause so that it will pass in main and 5.5 to avoid future conflicts.
@swift-ci please test |
Build failed |
@swift-ci please test Linux platform |
Build failed |
@swift-ci please test Linux platform |
Cherry-picks #37441
When compiling with allow errors, it's possible to have invalid
inherited types - both null and ErrorType.
Cleaned up the tests a little - moved the majority of
Frontend/allow-errors.swift into separate files in
Serialization/AllowErrors and use split_file.py instead of #defines.
Resolves rdar://78048470