Filter -is:module
Filters which are available for
select,
updateWhere
and
deleteWhere. Each filter constructor specifies the field
being filtered on, the type of comparison applied (equals, not equals,
etc) and the argument for the comparison.
Persistent users use combinators to create these.
Note that it's important to be careful about the
PersistFilter
that you are using, if you use this directly. For example, using the
In PersistFilter requires that you have an array- or
list-shaped
EntityField. It is possible to construct values
using this that will create malformed runtime values.
Type of filter and path to filter file.
Specify how filtering is done.
Keep all elements that satisfy a predicate, remove all that don't.
Example
>>> :kind! Eval (Filter ((>) 3) [1,2,3,0])
Eval (Filter ((>) 3) [1,2,3,0]) :: [Natural]
= [1, 2, 0]
No description available in the introspection data.
Memory-managed wrapper type.
Pseudocomponent that functions normally for explExists and
explMembers, but always return Filter for
explGet. Can be used in cmap as cmap $ (Filter :: Filter
a) -> b. Since the above can be written more consicely as
cmap $ (_ :: a) -> b, it is rarely directly. More
interestingly, we can define reusable filters like movables =
Filter :: Filter (Position, Velocity). Note that 'Filter c' is
equivalent to 'Not (Not c)'.
Class of values that support vector like operations
WalkType for filtering steps.
A filtering step is a step that does filtering only. It takes input
and emits some of them without any modification, reordering, traversal
actions, or side-effects. Filtering decision must be solely based on
each element.
A
Walk w is
Filter type iff:
(gSideEffect w == gIdentity) AND (gFilter w == w)
If
Walks
w1 and
w2 are
Filter type,
then
gAnd [w1, w2] == w1 >>> w2 == w2 >>> w1
As of Elastic 2.0, Filters are just Queries housed
in a Bool Query, and flagged in a different context.
'$[?(.foo == 42)]', '$[?(.foo > @.bar)]', etc.
Filters which are available for
select,
updateWhere
and
deleteWhere. Each filter constructor specifies the field
being filtered on, the type of comparison applied (equals, not equals,
etc) and the argument for the comparison.
Persistent users use combinators to create these.
Note that it's important to be careful about the
PersistFilter
that you are using, if you use this directly. For example, using the
In PersistFilter requires that you have an array- or
list-shaped
EntityField. It is possible to construct values
using this that will create malformed runtime values.
This type ensures that all signals generated from the event list share
the same sample rate.