[Dynamo] Add DictKeySetVariable to capture dict_keys passed outside of compiled region

[yanboliang]

Stack from ghstack (oldest at bottom):

• [Dynamo] Support dict_keys from nested dict object #143557
• [Dynamo] Rename Dict{View/Keys/Values} to Dict{View/Keys/Values}Variable #143547
• -> [Dynamo] Add DictKeySetVariable to capture dict_keys passed outside of compiled region #143374

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/143374

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit f0ce4aa with merge base b23f11c ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[yanboliang]

I understand that there is another DictKeys variable for tracking dict_keys, but it only derives from the dictionary itself. Within the compiled region, when users call dict.keys(), it essentially wraps the entire dictionary object. However, if dict_keys is passed from outside the compiled region, we can only access the mappingproxy via dict.keys().mapping.

I don’t think it’s necessary to add another DICT_KEYS guards for the mappingproxy again because:
1. If dict_keys is used together with the dictionary object, guards are already applied to the dictionary itself.
2. If dict_keys is used independently, its behavior is more like a set, we just need set similar guards.

This is why I introduced a new Dynamo variable rather than reuse the original DictKeys variable.

[yanboliang]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: Command git -C /home/runner/work/pytorch/pytorch rebase origin/main returned non-zero exit code 1

Rebasing (1/1)
Auto-merging test/dynamo/test_functions.py
CONFLICT (content): Merge conflict in test/dynamo/test_functions.py
error: could not apply 2ed14a20721... [Dynamo] Add DictKeySetVariable to capture dict_keys passed outside of compiled region (#143374)
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Could not apply 2ed14a20721... [Dynamo] Add DictKeySetVariable to capture dict_keys passed outside of compiled region (#143374)

Details for Dev Infra team

Raised by workflow job

[yanboliang]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here