Will Feng 05a7aaa742 Pass Tensor instead of Tensor& to torch::nn functionals that can change input in place (#30112) ... Summary: Pull Request resolved: https://github.com/pytorch/pytorch/pull/30112 Currently, we have torch::nn functionals that takes `input` as `Tensor&` in order to be able to in-place change `input`'s value. We likely shouldn't do this because it will prevent the following use case: ```cpp F::elu(torch::tensor(1), F::ELUFuncOptions().inplace(true)) ``` The solution is to change the type of `input` to `Tensor`, so that we can pass an rvalue into the functional. Test Plan: Imported from OSS Differential Revision: D18601580 Pulled By: yf225 fbshipit-source-id: 639a86eb62f6c986b0f20bf7e201983e83126e73		2019-11-19 16:11:39 -08:00
..
api	Pass Tensor instead of Tensor& to torch::nn functionals that can change input in place (#30112)	2019-11-19 16:11:39 -08:00
common	Trim libshm deps, move tempfile.h to c10 (#17019)	2019-02-13 19:38:35 -08:00
dist_autograd	Use std::shared_ptr for DistAutogradContext. (#29770)	2019-11-19 15:50:42 -08:00
jit	Mobile module forward() pass input by value. (#30060)	2019-11-18 22:33:38 -08:00
__init__.py	Add train() / eval() / is_training() to C++ ScriptModule API (#16044)	2019-02-01 13:07:38 -08:00