Gabriel Brown

@SamLubelsky Sorry for the delay. This is a nice workaround, thank you.

In case somebody stumbles upon this issue and also wants derivatives after adding, it's important to have `.as_explicit()` on both arguments to `derive_by_array()` here. ```python from sympy.tensor.array import derive_by_array from...

Sure, this is on my personal laptop running Manjaro Linux. All packages and applications are up to date. Here is the output of `cat /etc/lsb-release`: ``` DISTRIB_ID=ManjaroLinux DISTRIB_RELEASE=21.1.3 DISTRIB_CODENAME=Pahvo DISTRIB_DESCRIPTION="Manjaro...

I've been able to recreate this problem as recently as yesterday. However, after doing some compiler location, path and variable management on my side, as well as following the build...

It seemed anaconda was managing/providing my compilers (don't remember ever setting this up, so I just installed system-wide compilers instead). Then there were issues with CMake caches storing the old...

Unfortunately, this issue has appeared again. Based on `CMakeCache.txt` Anaconda is not managing any of the resources used in the build, and I've double checked the main ones. Steps (slightly...

I think having `*` be type dependent would make things harder, and I do prefer it as the elementwise operator. For what it's worth `*` ambiguity is apparently exactly why...

I think `@` is simple and familiar enough to Python/numpy users to be a solid contender. A second option (if viable) could be `#` which evokes "matrix multiplication" to me....

I've added default behavior per a conversation with @dmdunla.

Closing, as this PR was from the main branch of my fork by mistake. #301 has been opened as the replacement.