Should we stay on one level methods per type or use some sugar style api?

[cusspvz]

Sometimes we will face some methods that do just the same as other we have but with some difference on it, for those i'm thinking if we should place them on the same level or create sub ones.

Here is an example: we already have a method on Array type object called filter, which allows you to place a function to eval if a value should be filtered or not, inspite that we have also a method called randomFilter which does almost the same (filters array), but with a different propose.

My question here is if we should, on this cases, continue to apply one level for these methods (ƒ.Array.filter, ƒ.Array.randomFilter) or place similar methods inside of an existing one (ƒ.Array.filter, ƒ.Array.filter.random).

ping @gabrielpconceicao @brunocasanova @ajbloureiro

[brunocasanova]

I like more the one of the similar methods inside of an existing one!

[gabrielpconceicao]

similar methods inside of an existing one 👍

[ajbloureiro]

similar.methods.inside.of.an.existing.one