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
Instead of duplicating these overapproximate(X, Y) = convert(Y, X) methods, we could define one such fallback method that checks for hasmethod and otherwise throws an error.
The text was updated successfully, but these errors were encountered:
Yes, i thought about this recently. I think it is a good idea, but it may need to fix ambiguities for cases that are already generic in the set type, e.g. for overapproximate(::LazySet, Hyperrectangle), we would not like to use the convert fallback (always).
Instead of duplicating these
overapproximate(X, Y) = convert(Y, X)
methods, we could define one such fallback method that checks forhasmethod
and otherwise throws an error.The text was updated successfully, but these errors were encountered: