[random] Add generator arg to rand*_like APIs

[KarhouTam]

Fixes #165865

What this PR does?

• Add generator arg to rand*_like APIs (rand_like(), randn_like(), randint_like()).
• Add unit tests for rand*_like APIs
• Add corresponding arg docs
• Refactor rand*_like() codes in TensorFactories.cpp
• Add corresponding and former missed items in VmapModeRegistrations.cpp

Example (using rand_like())

gen0 = torch.Generator()
gen1 = torch.Generator()
gen2 = torch.Generator()

gen0.manual_seed(42)
gen1.manual_seed(42)
gen2.manual_seed(2025)

tensor = torch.empty(10)

t0 = torch.rand_like(tensor, generator=gen0)
t1 = torch.rand_like(tensor, generator=gen1)
t2 = torch.rand_like(tensor, generator=gen2)

assert t0 == t1
assert t2 != t0
assert t2 != t1

cc @pbelevich @albanD

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCm failures during provisioning step due to network issues

✅ You can merge normally! (1 Unrelated Failure)

As of commit 2394bc2 with merge base e67e3d9 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• trunk / macos-py3-arm64 / test (default, 3, 3, macos-m1-stable) (gh) (disabled by #156921 but the issue was closed recently and a rebase is needed to make it pass)
  test/dynamo/test_structured_trace.py::StructuredTraceTest::test_compiled_autograd_attribution

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

[KarhouTam]

@pytorchbot label "module: random" "release notes: random"

[pytorch-bot]

Didn't find following labels among repository labels: release notes: random

[github-actions]

Attention! native_functions.yaml was changed

If you are adding a new function or defaulted argument to native_functions.yaml, you cannot use it from pre-existing Python frontend code until our FC window passes (two weeks). Split your PR into two PRs, one which adds the new C++ functionality, and one that makes use of it from Python, and land them two weeks apart. See https://github.com/pytorch/pytorch/wiki/PyTorch's-Python-Frontend-Backward-and-Forward-Compatibility-Policy#forwards-compatibility-fc for more info.

---

Caused by:

• aten/src/ATen/native/native_functions.yaml

[KarhouTam]

@pytorchbot label "release notes: python_frontend"

[KarhouTam]

I think this PR is ready for review!
PTAL. @albanD @pbelevich

[KarhouTam]

Hi, @albanD @malfet @bobrenjc93. PTAL. If anything this PR missed, please let me know.

[albanD]

SGTM!
Thanks for taking the time to look at this one!

[albanD]

@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