You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I optimize code using the suggestions from herbie, I get caught in a catch-22. the optimized expression often contains the original expression as one of its several branches.
Some way to filter these out would be ideal.
The simplest option would be to allow the use of an {-# ANN #-} pragma on a function to tell herbie to ignore it.
Even better would be a way to tell herbie the filtered range of arguments that can reach a sub-expression, so that it can know to avoid supplying better approximations for inputs that are outside of the domain.
The text was updated successfully, but these errors were encountered:
Does 1c5f8ae do something similar to what you had in mind?
Even better would be a way to tell herbie the filtered range of arguments that can reach a sub-expression, so that it can know to avoid supplying better approximations for inputs that are outside of the domain.
I agree, but the Herbie progam doesn't currently support this AFAIK.
When I optimize code using the suggestions from
herbie
, I get caught in a catch-22. the optimized expression often contains the original expression as one of its several branches.Some way to filter these out would be ideal.
The simplest option would be to allow the use of an
{-# ANN #-}
pragma on a function to tellherbie
to ignore it.Even better would be a way to tell
herbie
the filtered range of arguments that can reach a sub-expression, so that it can know to avoid supplying better approximations for inputs that are outside of the domain.The text was updated successfully, but these errors were encountered: