Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[mypyc] Avoid boxing/unboxing when coercing between tuple types #14899

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.

Sign up for GitHub

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
JukkaL merged 2 commits into from
Mar 20, 2023
Merged

[mypyc] Avoid boxing/unboxing when coercing between tuple types #14899

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1fd6093
[mypyc] Avoid boxing/unboxing when coercing between tuple types
JukkaL Mar 12, 2023
72d9a9c
Only run test on 64 bit archictecture
JukkaL Mar 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Only run test on 64 bit archictecture
  • Loading branch information
@JukkaL
JukkaL committed Mar 14, 2023
commit 72d9a9cf8b8db68d3f65bde1a3b1cbb648c632f2
2 changes: 1 addition & 1 deletion mypyc/test-data/irbuild-i64.test
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2079,7 +2079,7 @@ L2:
keep_alive x
return r6

[case testI64ConvertBetweenTuples]
[case testI64ConvertBetweenTuples_64bit]
from __future__ import annotations
from mypy_extensions import i64

Expand Down