You're right, I did read very quickly on this but it's the
standard OR operator being used differently:
Well, I think that is a "good thing" if the language allows you to reuse the syntax (operator overload) through library implementations without changing the compiler.
So there would seem be be a need here since this is not yet
implemented if I am right.
Not yet, but being flexible to convert from ranges to *ANY* kind of container may be challenging...
We are also trying to avoid macros... they are not module-friendly, not bounded to the type system, among many other issues: