No. I completely understand, and you should choose whichever approach makes the most sense to you. Personally, I prefer composing and passing functions rather than โrenamingโ built-in onesโespecially when working in a team or on a shared codebase. If I ever have trouble remembering what a specific Enum.filter does, Iโll simply define a function like this:
def reject(item), do: โฆ
Enum.filter(items, &reject/1)
And Iโd use the same strategy for functions like select and others.
(Of course there is Enum.reject/2, but used a โrejectโ fun here, for brevity)