Move FunctionSchema implementations to cpp file

[ezyang]

Stack from ghstack (oldest at bottom):

• -> Move FunctionSchema implementations to cpp file #133856

Signed-off-by: Edward Z. Yang ezyang@meta.com

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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! (8 Unrelated Failures)

As of commit d951198 with merge base 907c32f ():

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

• trunk / linux-focal-rocm6.1-py3.8 / test (default, 1, 2, linux.rocm.gpu) (gh) (disabled by #134519)
  inductor/test_torchinductor.py::GPUTests::test_mutable_custom_op_fixed_layout2_cuda

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• linux-binary-manywheel / manywheel-py3_9-cuda11_8-split-test / test (gh) (trunk failure)
• linux-binary-manywheel / manywheel-py3_9-cuda11_8-test / test (gh) (trunk failure)
• linux-binary-manywheel / manywheel-py3_9-cuda12_1-split-test / test (gh) (trunk failure)
• linux-binary-manywheel / manywheel-py3_9-cuda12_1-test / test (gh) (trunk failure)
• linux-binary-manywheel / manywheel-py3_9-cuda12_4-split-test / test (gh) (trunk failure)
• linux-binary-manywheel / manywheel-py3_9-cuda12_4-test / test (gh) (trunk failure)
• pull / linux-jammy-py3.8-gcc11 / test (distributed, 1, 2, amz2023.linux.2xlarge) (gh) (trunk failure)
  distributed/_tensor/test_dtensor_ops.py::TestDTensorOpsCPU::test_dtensor_op_db_nn_functional_gaussian_nll_loss_cpu_float32

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

[bdhirsh]

did you end up here because of binary size bloat or because you wanted to tweak and print and not wait 10 mins for a recompile 😛

[ezyang]

I thought I wanted to tweak but it turns out I don't need to lol. Just some BE.

[albanD]

SGTM !
Some include needs tweaking

[ezyang]

@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

[ezyang]

@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