-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib] Drop some @available(introduced:...) #10994
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
These annotations make it hard to write code that works in both Swift 3 and Swift 4, so if they aren't needed we should remove them.
@swift-ci Please test |
@swift-ci Please test source compatibility |
@swift-ci Please smoke benchmark |
In Swift 3 shifts used to be defined on the concrete integer types, so the right-hand-side value in the shift expression could define a type for the result, as in `1 << i32` would have the type Int32. Swift 4 makes shift operators heterogeneous, so now `1 << i32` will result in an Int, according to the type of the left-hand-side value, which gets a default type for integer literals.
Build comment file:Optimized (O)No Changes (338)
Unoptimized (Onone)No Changes (338)
Hardware Overview
|
The source compatibility failures all seem to be compiler crashes of one sort or another. We have bugs to report... |
Source compatibility failures appear to be unrelated, as they are failing here on master: https://ci.swift.org/view/Source%20Compatibility/job/swift-master-source-compat-suite/807/artifact/swift-source-compat-suite/ |
@swift-ci Please test source compatibility |
1 similar comment
@swift-ci Please test source compatibility |
These |
@swift-ci Please Test Source Compatibility |
1 similar comment
@swift-ci Please Test Source Compatibility |
These annotations make it hard to write code that works in both Swift 3 and Swift 4, so if they aren't needed we should remove them.