Mike Mullen

Jumping on since I am also interested in running MatX on WSL2 and built successfully by staying on the v0.5.0 tag, and cherry-picking the commit @cliffburdick mentioned [here](https://github.com/NVIDIA/MatX/pull/467). That being...

Ah, it gets back to the managed memory, since fft_conv relies on managed memory for the () operator. Outlined [here](https://github.com/NVIDIA/MatX/blob/cf6aeb30ffa2f1cfde3ec442eba123b86ea8eefe/docs_input/notebooks/01_introduction.ipynb#L168) for why I get a seg fault.

I cannot replicate this issue using master commit `1eb6bca` (most recent as of this morning). Using the latest driver with an RTX 3050. I even extended the loop to 10k...

I use cross products quite a bit and would be interested in implementing this. Anything I should be aware of regarding intended implementation or anything?

Great thanks! I'll start on this sometime this week.

As a matter of convention in MatX, are assertions best defined in the constructor for a class template specialization (e.g. like in `polyval.h`) or in the `Exec` method, like in...

This hasn't dropped off my radar, just haven't had a chance to look at it since implementing the runtime checks.

Finally got around to this! Have some unit tests put together locally but unsure where to put the documentation. Would it make sense to place it in `docs_input/api/linalg/other`? Logic being...