Re:When is a recursive function not a recursive function?
by mackwic on Sunday October 05, 2014 @05:23AM
(#8411850)
Because of clarity ?
A function can have a really broad use, and the particular use case is unclear when you call it. In this hypothetical but likely situation, aliasing the general function to a more-specific name is good neighbor behavior, isn't it ?
Note that it's particularly frequent when you are used to code with lot of purity and high-order applications, when you define few pure functions with lot of parameters and specialize them in your modules by fixing some of the parameters. Sometimes you don't want to (or can't) fix a parameter but still want the function to have the specialized name.
A function can have a really broad use, and the particular use case is unclear when you call it. In this hypothetical but likely situation, aliasing the general function to a more-specific name is good neighbor behavior, isn't it ?
Note that it's particularly frequent when you are used to code with lot of purity and high-order applications, when you define few pure functions with lot of parameters and specialize them in your modules by fixing some of the parameters. Sometimes you don't want to (or can't) fix a parameter but still want the function to have the specialized name.