[1/N] Remove inclusion of ATen/core/Array.h

[cyyever]

The functionality of Array.h is largely overlapped with std::array and it should be safe to use std::array instead.

[pytorch-bot]

🔗 Helpful Links

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

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

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

• [DomainsOnly] Jobs fail with GLIBC version not found
• Failure to deploy Self-Hosted runners - High Queue Times and canceled jobs

✅ You can merge normally! (3 Unrelated Failures)

As of commit 057cf7a with merge base 7360287 ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• linux-binary-manywheel / manywheel-py3_10-xpu-test (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: a prune operation is already running
• linux-binary-manywheel / manywheel-py3_12-xpu-test (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: a prune operation is already running
• macos-arm64-binary-libtorch-cxx11-abi / libtorch-cpu-shared-with-deps-cxx11-abi-build (gh) (similar failure)
  cp: /Users/runner/work/pytorch/pytorch/pytorch/any_wheel/torch/lib/libomp.dylib: No such file or directory

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

[cyyever]

@pytorchbot label ciflow/binaries

[ezyang]

Do you remember why Array.h was added in the first place? c++17 backport?

[cyyever]

Do you remember why Array.h was added in the first place? c++17 backport?

I don't know, but I guess it is before C++14 was adopted?

[cyyever]

@pytorchbot label ciflow/binaries

[cyyever]

@ezyang CUDA 12.1 ptx keeps crashing after these changes. It seems that we have to delay the merge.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[cyyever]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

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

[cyyever]

@pytorchmergebot merge -f "Fix transitive inclusion"

[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