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

fix: Consider type when deciding whether to pack up returns #212

Merged
merged 1 commit into from
May 14, 2024

Conversation

mark-koch
Copy link
Collaborator

@mark-koch mark-koch commented May 14, 2024

Fixes #211

@mark-koch mark-koch requested a review from croyzor May 14, 2024 09:16
Copy link
Collaborator

@croyzor croyzor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@codecov-commenter
Copy link

codecov-commenter commented May 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.64%. Comparing base (324f2ee) to head (f3eb309).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #212   +/-   ##
=======================================
  Coverage   90.63%   90.64%           
=======================================
  Files          46       46           
  Lines        4722     4724    +2     
=======================================
+ Hits         4280     4282    +2     
  Misses        442      442           

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

@mark-koch mark-koch merged commit 4f24a07 into main May 14, 2024
4 checks passed
@mark-koch mark-koch deleted the fix/unary-tuple branch May 14, 2024 09:21
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.

Unary tuple returns are handled incorrectly
3 participants