Skip to content
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

Properly handle conditional expression within parens as RHS of assignment #1140

Merged
merged 2 commits into from
Jan 31, 2025

Conversation

msridhar
Copy link
Collaborator

Fixes #1127

Our previous (hacky) logic for determining the type of a conditional expression on the RHS of an assignment did not account for the expression possibly being enclosed in parentheses.

Copy link

codecov bot commented Jan 31, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.24%. Comparing base (90265c5) to head (7ff1e58).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #1140   +/-   ##
=========================================
  Coverage     88.24%   88.24%           
- Complexity     2260     2261    +1     
=========================================
  Files            85       85           
  Lines          7305     7309    +4     
  Branches       1457     1458    +1     
=========================================
+ Hits           6446     6450    +4     
  Misses          431      431           
  Partials        428      428           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@msridhar msridhar enabled auto-merge (squash) January 31, 2025 22:54
@msridhar msridhar merged commit 18a0a68 into master Jan 31, 2025
12 checks passed
@msridhar msridhar deleted the issue-1127 branch January 31, 2025 23:04
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.

Mismatched nullability of type parameters in sub-expression
2 participants