Seems like a pretty easy example to make practically, for map have a collection of things, say balls or black. Pick up each one and do a thing to them, paint them blue for example.
For filter do the same except have two different colour balls, if they are yellow they get thrown away, of they are blue they get put in a bucket.
A for loop doing exactly the same you would need to explain the topic at hand, as well as explain iterating an index etc...
Maps and filters also require understanding of higher order functions and the very idea of passing function around as a value. I would argue that implementing map/filter with a loop and then demonstrating how this pattern is generalized as .map()/.filter() functions is better and more accessible
Nobody in school ever tells you that there are glossaries on Wikipedia that tell you the meaning of the symbols. You're supposed to figure it out yourself using vibes.
The way mathematic notation is taught is inherently unstructured. You're expected to just get it.
I often see people make the mistake of trying to teach inappropriately abstract things to small children, because that's what the pros do, and we want the little kids become pros as soon as possible. Problem is, trying to skip the fundamentals is only harmful in long term.
First kids need to learn what all that stuff means, and then we can proceed to teach them the shortcuts.
That said, as a person who moderately enjoyed math in high school and university, this functional notation would make me hate math infinitely more. It's would look like Lisp, which, at high level, looks just as cryptic as algebra. The sheer amount of braces and mistakes that would be made when reading and writing them is nauseating.
Infix notation, for all its flaws, provides important visual aid for understanding the structure of the expression (the sum of two fractions looks very different from fraction of two sums for example). Whereas with functional notation it's like working on linear textual representation of abstract syntax tree. Trust me, nobody wants to read, write or transform one by hand
https://aplwiki.com/wiki/Comparison_with_traditional_mathema...
;-)
What I should really do is create myself a cheat sheet of symbols to code...
Also it should be sum(x+3, x, 1, 4) since you need to encode what the iterator variable is as well.
Edit: Oh wait, someone else mentions map/filter, did they mean this as a combination of range->map->sum and the latter two numbers are the range portion, like sum(map(x+3, 1..4)) ?
Edit2: And now I'm remembering sigma. I think it would have been more obvious to me if the order was flipped and your issue handled the way it is in that notation: sum(x=1, 4, x+3), though I'd still prefer the range notation: sum(x=1..4, x+3)
Granted I always found sigma a bit quirky for separating the range ends like that. Either x below and 1..4 above, or x=1..4 below/above would have been more intuitive.
But it's just a notation you learn once and then you know it.
Interestingly mathematical symbols in the past also regularly evolved. Then at some point we just stopped doing that and get stuck in a time which is arguably no longer especially appropriate. So we're left with rather inconsistent symbols, oft reused in different contexts, and optimized for written communication.