Name proposal for lazy operations: past tense

I've been happy to seperate the semantics of greedy-vs-lazy operations into seperate functions, like map vs mapview and group vs groupview. However, the view suffix is a little tiresome.

I'm wondering if we should follow the example set by Base.Broadcast which uses broadcast(...) = materialize(broadcasted(...)), where broadcasted is more-or-less a lazy version of broadcast and materialize is something that behaves a bit like copy when necessary.

That would be something like:

• mapview -> mapped.
• groupview -> grouped.
• Lazy join functions ending in joined instead of join.
• A new filtered for lazy filter.
• product is a noun, not a verb, and seems fine being lazy.
• flatten vs flattened?
• We've been discussing splitdims at Base and slice/slices seems like a possible naming. sliced could be a lazy version?
• etc...

Does anyone have any thoughts or opinions?

Review the existing map/mapview, group/groupview, lazy join, filter, flatten, splitdims, slice, and product APIs named in the issue. First determine whether the project has settled on a naming convention; done would require an agreed naming plan for the affected lazy operations, rather than a single isolated edit.