-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Enable NonEscapable types by default and move lifetime dependence support under a new feature #77637
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
Conversation
e41be3e
to
5b73762
Compare
@swift-ci test |
5b73762
to
c08c815
Compare
@swift-ci test |
0dddf22
to
ac38a23
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No concerns from me!
ac38a23
to
083de18
Compare
@swift-ci test |
134e000
to
d6f9ccc
Compare
@swift-ci test |
preset=oss-swift-test-stdlib-with-toolchain |
d6f9ccc
to
09e1d80
Compare
@swift-ci test |
preset=oss-swift-test-stdlib-with-toolchain |
09e1d80
to
a5c5c20
Compare
@swift-ci test |
a5c5c20
to
2b6c053
Compare
@swift-ci test |
2b6c053
to
503b8ad
Compare
@swift-ci test |
Without this, supported old compilers which don't recognize LifetimeDependence feature but recognize the NonEscapableTypes feature will run into lifetime dependence inference errors on the implicit initializer generated for the stdlib's swiftinterface
503b8ad
to
92782a0
Compare
@swift-ci test |
SE-0446 is accepted - Promote
NonescapableTypes
feature into a LANGUAGE_FEATURE. Move lifetime dependence support under a new experimental flag.LifetimeDependence
feature flag ensures Span's use of lifetime features are appropriately printed and work with older compilers which don't understand them yet.