[ 
https://issues.apache.org/jira/browse/MATH-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772273#action_12772273
 ] 

Phil Steitz commented on MATH-313:
----------------------------------

I agree with Luc on limiting abstract infrastructure to what we have practical 
use cases for.  See "guiding principles" on the home page.  I am +0 on adding 
ComposableFunction.  One thing to consider is do we require that Composable 
functions be total and finite-valued.  If not, documenting and debugging 
NaN/Inf/Exceptions could be tricky for users.  Also, do we require that 
composition be only "with" ComposableFunctions?  If yes to the second question, 
you don't need both pre- and postCompose.  I guess another thing to think about 
is inverses.  I am interested in seeing more on practical use cases for these 
things.

> Functions could be more object-oriented without losing any power.
> -----------------------------------------------------------------
>
>                 Key: MATH-313
>                 URL: https://issues.apache.org/jira/browse/MATH-313
>             Project: Commons Math
>          Issue Type: New Feature
>    Affects Versions: 2.0
>         Environment: all
>            Reporter: Jake Mannix
>             Fix For: 2.1
>
>
> UnivariateRealFunction, for example, is a map from R to R.  The set of such 
> functions has tons and tons of structure: in addition to being an algebra, 
> equipped with +,-,*, and scaling by constants, it maps the same space into 
> itself, so it is composable, both pre and post.
> I'd propose we add:
> {code}
>   UnivariateRealFunction plus(UnivariateRealFunction other);
>   UnivariateRealFunction minus(UnivariateRealFunction other);
>   UnivariateRealFunction times(UnivariateRealFunction other);
>   UnivariateRealFunction times(double scale);
>   UnivariateRealFunction preCompose(UnivariateRealFunction other);
>   UnivariateRealFunction postCompose(UnivariateRealFunction other);
> {code}
> to the interface, and then implement them in an 
> AbstractUnivariateRealFunction base class.  No implementer would need to 
> notice, other than switching to extend this class rather than implement 
> UnivariateRealFunction.
> Many people don't need or use this, but... it makes for some powerfully easy 
> code:
> {code}UnivariateRealFunction gaussian = 
> Exp.preCompose(Negate.preCompose(Pow2));{code}
> which is even nicer when done anonymously passing into a map/collect method 
> (a la MATH-312).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to