Dustin Getz

Consider introducing an operator `:!` to indicate "this is an expected failure acknowledging a bug, until fixed it should not fail the suite so count it as pass"

I propose to rename `thrown?` to `throws?` or even `:throws`

This example is just begging for memory variables to destructure on client/server ```clojure (ns user.photon_compiler (:require [hyperfiddle.photon :as p] [hyperfiddle.photon-impl.compiler :refer [analyze]] [hyperfiddle.photon-impl.runtime :as r :refer [emit]] [hyperfiddle.rcf :refer [tests]]))...

1. How is `m/replay` different from `m/stream` and `m/signal` 2. Can you provide a continuous time example under the proposed syntax?

https://clojurians.slack.com/archives/C7Q9GSHFV/p1661662217708859

I am running with this patch locally for a bit

In my current opinion tests should discard the last value and return nil, in practice I do not recall ever getting value from this and only being annoyed when the...

It also makes the nextjournal notebook experiments a bit worse - https://nextjournal.com/dustingetz/datafynav-implementations-for-javaiofile – I see these notebooks as essays or docs and I want to carefully direct the user's attention...

duplicate https://github.com/hyperfiddle/rcf/issues/61

Fixed in https://github.com/hyperfiddle/rcf/commit/83b90b423775220c2448513b11036b2a65ad17c7