Skip to content

[CSOptimizer] Don't consider CGFloat widening when explicit initializ… #78949

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 28, 2025

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Jan 27, 2025

…er is used

Disable implicit CGFloat -> Double widening conversion if argument is an explicit call to CGFloat initializer.

…er is used

Disable implicit `CGFloat` -> `Double` widening conversion if
argument is an explicit call to `CGFloat` initializer.
@xedin xedin requested a review from hborla as a code owner January 27, 2025 17:58
@xedin
Copy link
Contributor Author

xedin commented Jan 27, 2025

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented Jan 27, 2025

@swift-ci please test source compatibility

@xedin
Copy link
Contributor Author

xedin commented Jan 27, 2025

@swift-ci please test source compatibility debug

1 similar comment
@xedin
Copy link
Contributor Author

xedin commented Jan 27, 2025

@swift-ci please test source compatibility debug

@xedin
Copy link
Contributor Author

xedin commented Jan 28, 2025

vapor_jwt and vapor_jwt-kit projects started UPASS'ing (swiftlang/swift-source-compat-suite#970).

@xedin xedin merged commit 248c026 into swiftlang:main Jan 28, 2025
6 of 7 checks passed
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.

1 participant