Dmitry

Good solution for hard problem 👍 I think it will greatly improve interoperability in applications

Which tests are failed?

Is it working now?

I suggest to go deeper ```ts guard({ clock, filter: { mode: 'every', units: [$flagA, $flagB], }, target, }) guard({ clock, filter: { mode: 'some', units: [$flagA, $flagB], }, target, })...

Yep, you get the idea

Is not obvious why `'every'` use case is better to be default than `'some'`

> intuitively implied as a set of preconditions Indeed. "Set of something" don't imply how that set will be used. For example, array in `clock` is obviously an "or" clause...

I’ve had time to think about this proposal. First, the case described by the author ("all") is much more important than the one I suggested ("some"), that is, we can...

> What about to make .map() Breaking change to `.map` is pretty obvious move, so it not make this idea further, we are not ready to discuss maps > And...

> StoreSource — can be used only as a source/clock Preventing that code ```ts const $foo: Store sample({ clock: $foo, source: some, target: bar, }) ``` means that update of...