Taken from the devel mailing list in July 2021. Quoting Artur:
"An element could be a row, column or an item in some array. ... In principle, this is similar to Pandas's apply function: https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.apply.html"
Jack remarked: "having something that help avoiding explicit loops sounds very good to me."
A cheap idea: If it were possible for a user-written hansl function to accept an unspecified "array" as an argument type (and also as return value...), then it should be fairly easy to have this in hansl. The function maybe would not even have to check whether it is getting matrices, strings, or whatever. This would be somehow similar to the generic "numeric" argument type.
Something like this:
<pseudo-hansl></pseudo-hansl>
We discussed that this is nice to have, but not top priority.
It was discussed again; getting this done in a reasonably efficient way (not just calling the same function many times in an internal loop) appears to be not so easy. Also, in the meantime more hansl functions have been enabled to work on arrays element-wise. So it's not so clear anymore whether this should be pursued.
OK, we said that the cost-benefit relation is not good enough, and writing an explicit hansl loop is not so bad these days anyway. So we're closing this.