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
The problem may be restated: shall the base do it -or- shall it let us do it when needed.
If the compiler handles this issue by catching all the call eg. filter(s::Any, itr::Any) is for me, this will lead to both bottleneck and opaque interface/interop at module boundary.
It should be defined? It would be consistent with the other methods:
I get that it's not a type-stable operation except in special cases like
filter(isa(Int), (2,3.0,4))
, but it would still be occasionally convenient.The text was updated successfully, but these errors were encountered: