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
For some integral(f, geometry...), our API currently requires f::Function. However, the only real requirement for f internally is that it must expose a method f(::Point), which can be fulfilled by other callables. For example:
struct Widget
...end
(w::Widget)(p::Point) =...
w =Widget(...)
geometry =...integral(w, geometry)
Enabling this would require
a sweep of all integral and _integral methods to remove type params from f
updating documentation, e.g. mentioning this fact in the README
evaluating whether this causes any dispatch issues
adding a test that specifies a callable non-Function for f
The text was updated successfully, but these errors were encountered:
I don’t think it’s strictly breaking, but I added the label as a marker to remember that I’d like to complete this one prior to this upcoming breaking v0.16 release.
For some
integral(f, geometry...)
, our API currently requiresf::Function
. However, the only real requirement forf
internally is that it must expose a methodf(::Point)
, which can be fulfilled by other callables. For example:Enabling this would require
integral
and_integral
methods to remove type params fromf
Function
forf
The text was updated successfully, but these errors were encountered: