Add the Mode section in the extending doc

[albanD]

Cover the basic principles of Mode and an example on how to use them and their behavior.

[pytorch-bot]

🔗 Helpful Links

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

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit 6391553 with merge base a3e5ec4 ():

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

• trunk / linux-focal-rocm5.6-py3.8 / test (default, 2, 3, linux.rocm.gpu, unstable) (gh)
• trunk / linux-focal-rocm5.6-py3.8 / test (default, 3, 3, linux.rocm.gpu, unstable) (gh)

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

[janeyx99]

cool pr! left some grammatical nits. appreciated the example, but i don’t come away knowing which mode i should use (the blatant difference to me seems to be aten vs torch api). a question i still don’t quite know the answer to: when should dispatch mode be used with subclasses?

also cc @drisspg who mentioned wanting a wiki like this before

[janeyx99]

I think you can do more here to explain when someone would use torch function vs torch dispatch

[albanD]

The two previous sections should be describing these in details already.
And I do plan to add an intro with the big "when to use what" diagram. I will do that in a follow up!

[janeyx99]

ah yes

[albanD]

@pytorchbot merge -r

[pytorch-bot]

This PR needs to be approved by an authorized maintainer before merge.

[janeyx99]

@pytorchbot merge -r

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Successfully rebased extending_doc_update onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout extending_doc_update && git pull --rebase)

[pytorchmergebot]

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Details for Dev Infra team

Raised by workflow job

[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