We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
md5: 8a0bd131195677f0720f33b822428475
Issue Description:
Placing @avilable(iOS, obsoleted) above a function is not preventing the execution of that function on newer platforms.
Example:
override func viewDidLoad() { super.viewDidLoad() testFunc() } @available(iOS, obsoleted: 10.0) func testFunc() { print("testFunc") }
@available(iOS, obsoleted: 10.0) override func invalidationContext(forPreferredLayoutAttributes preferredAttributes: UICollectionViewLayoutAttributes, withOriginalAttributes originalAttributes: UICollectionViewLayoutAttributes) -> UICollectionViewLayoutInvalidationContext
The text was updated successfully, but these errors were encountered:
Yeah, we don't have availability checking for "max allowed OS" implemented yet.
Sorry, something went wrong.
Comment by Jwa, Min-Kyung (JIRA)
I wonder when this option will be applied in Swift.
I believe this is implemented. The following fails to type check for a deployment target > macOS 11 with the Swift 5.6 compiler:
@available(macOS, obsoleted: 11.0) func test() {} // note: 'test()' was obsoleted in macOS 11.0 test() // error: 'test()' is unavailable in macOS
No branches or pull requests
Additional Detail from JIRA
md5: 8a0bd131195677f0720f33b822428475
Issue Description:
Placing @avilable(iOS, obsoleted) above a function is not preventing the execution of that function on newer platforms.
Example:
The text was updated successfully, but these errors were encountered: