Will Feng 11172c19be codemod at::ArrayRef and torch::IntArrayRef to std::vector in C++ API tests (#27884) ... Summary: `at::ArrayRef` / `torch::IntArrayRef` should be discouraged in user code, because users might not be aware of the fact that it doesn't own the underlying data, which already leads to memory access bugs when they try to write the following: ```cpp auto expected_sizes = torch::IntArrayRef({2, 16, 6}); // The memory that represents `{2, 16, 6}` is released after this line ASSERT_EQ(output.sizes(), expected_sizes); // `expected_sizes` is pointing to invalid memory region ``` This PR changes all usage of `at::ArrayRef` and `torch::IntArrayRef` to the corresponding `std::vector` version, so that users won't pick up the habit of using `ArrayRef` by looking at the test code. Pull Request resolved: https://github.com/pytorch/pytorch/pull/27884 Differential Revision: D17921646 Pulled By: yf225 fbshipit-source-id: 461e79fc22b598aac230d36cc028085ce6cbe937		2019-10-14 18:00:30 -07:00
..
api	codemod at::ArrayRef and torch::IntArrayRef to std::vector in C++ API tests (#27884)	2019-10-14 18:00:30 -07:00
common	Trim libshm deps, move tempfile.h to c10 (#17019)	2019-02-13 19:38:35 -08:00
dist_autograd	add known worker ids to distributed autograd context (#26324)	2019-10-14 10:43:09 -07:00
jit	module dedupe (#26666)	2019-10-12 09:51:57 -07:00
__init__.py	Add train() / eval() / is_training() to C++ ScriptModule API (#16044)	2019-02-01 13:07:38 -08:00