Hi Anjali!



 anjali411:

However as I mentioned above, you can still get the old conj behavior if you use torch.conj_physical (out-of-place operation instead of a view operation)


I do agree that the 1.10 behavior of .conj() is unexpected.
Would it make sense to rename the new .conj() to .conj_view()?  If
so, I would then vote for leaving .conj_physical() as is to help make
clear what is going on.  (Renaming .conj_physical() to .conj() might
make use of .conj() the tempting default, tricking people into the
aforementioned performance hit.)
Best.
K. Frank