Remove c10::either

[cyyever]

Time to remove it.

cc @albanD

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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! (1 Unrelated Failure)

As of commit 6bd4b1f with merge base 67c8ad7 ():

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

• trunk / linux-focal-rocm5.7-py3.8 / test (default, 1, 1, linux.rocm.gpu) (gh)

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

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[cyyever]

@albanD A missing change was submitted, have to re-import

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[albanD]

@pytorchbot merge

Fixed internal failures in the linked diff.

[pytorch-bot]

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

[albanD]

@pytorchbot merge

[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

[cyyever]

@pytorchbot label "topic: not user facing"

[cyyever]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

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

[albanD]

I have to reapply internal patch and everything. Please don't merge

[cyyever]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

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

[cyyever]

@albanD Should we merge it?

[albanD]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

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

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[albanD]

@pytorchbot merge

Sorry for the delay, take forever to get my internal env setup again every time. Should be good now

[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