Make sparse empty constructors specialize instead of fail on symbolic inputs

[ezyang]

Stack from ghstack (oldest at bottom):

• Stop immediately specializing common constants 0/1 for plain int #128327
• -> Make sparse empty constructors specialize instead of fail on symbolic inputs #129983

Exercised in #128327

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

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 2 New Failures

As of commit ff7958a with merge base 1e27af3 ():

NEW FAILURES - The following jobs have failed:

• inductor / rocm6.1-py3.8-inductor / test (inductor, 2, 2, linux.rocm.gpu.2) (gh)
  test_ops 1/5 failed!
• trunk / win-vs2019-cpu-py3 / test (default, 1, 3, windows.4xlarge.nonephemeral) (gh)
  'Test'

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

[ezyang]

@pytorchbot merge -f "failures look unrelated"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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