It seems like the only way out of this pickle is to either mark containers you want to iterate (or scalars you don’t want to iterate). Anyways, here’s a proposal:
A lazy call object contains both a function and its arguments. For example,
LazyCall((a, b) -> a + b + 1, (A, B))
There is special syntax for making a lazy call.
.( ~A + ~B) is syntactic sugar for the above
You can call a function on a LazyCall, also with special syntax:
broadcast.( ~A + ~B + 1)
You could just as easily do:
filter.( ~A > 1)
Sorry for possibly derailing the thread. I just though I’d mention that an abstraction I’ve been working on for a long time could unequivocally sort out this conflict.
Here is another idea: ~ alone could signify an anonymous function, so
.( ~ + 1)
x - x + 1
A |> .( ~ + 1)
could be a syntax for chaining