Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix order of steal/unborrow in tuple unpacking#18732

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
JukkaL merged 1 commit intopython:masterfromilevkivskyi:fix-steal-unborrow
Feb 25, 2025

Conversation

@ilevkivskyi
Copy link
Member

Currently, although globally the refcount is correct, it may briefly touch 0 if a target of unpacking in unused, e.g._, _, last = some_tuple. This can be prevented by placing steal before unborrow (which IMO should be the recommended way, if I understand the logic of these terms correctly).

Copy link
Collaborator

@JukkaLJukkaL left a comment

Choose a reason for hiding this comment

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

I think you are right. This is pretty subtle, but it appears the old logic was wrong.

@JukkaLJukkaL merged commit34f6f6a intopython:masterFeb 25, 2025
12 checks passed
@ilevkivskyiilevkivskyi deleted the fix-steal-unborrow branchFebruary 25, 2025 16:21
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@JukkaLJukkaLJukkaL approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ilevkivskyi@JukkaL

[8]ページ先頭

©2009-2025 Movatter.jp