You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking at #16606 this morning and am not 100% on-board with the dropdims solution - as commented by others, I feel like it obfuscates the purpose of the code, which is performing the reduction.
I just noticed that, working with a 1-dimensional array, a reduction gives me a single value, automatically dropping the dimension. This seems inconsistent with behaviour for higher-dimensional arrays. Is this intended?
The text was updated successfully, but these errors were encountered:
Thanks for the report. However, the behavior is consistent and has nothing to do with the dimensionality of the input: reducers without the dims keyword argument return a scalar:
I was looking at #16606 this morning and am not 100% on-board with the dropdims solution - as commented by others, I feel like it obfuscates the purpose of the code, which is performing the reduction.
I just noticed that, working with a 1-dimensional array, a reduction gives me a single value, automatically dropping the dimension. This seems inconsistent with behaviour for higher-dimensional arrays. Is this intended?
The text was updated successfully, but these errors were encountered: