Hoàng

I do have some ideals about this, and would like to help. `SplitByType` would be very welcomed, as my app usually required something similar to that.

I'm currently using something like this https://gist.github.com/HollandDM/446bb41a8c89607b140d3bf3297b2a92. This macro's main feature is to turn a bunch of code from this: ```scala sealed trait Foo final case class Bar(strOpt: Option[String]) extends...

@raquo Don't worry, I can still use my internal implementation in the mean time. Take your time!

I encountered a case in the past that also required a combo of `split` and `flatMap`. It basically looks like this: ```scala val inputsSignal: Signal[List[I]] = ??? def veryExpensiveFn(input: I):...

After some reading, I think [Angular's push & pull approach](https://betterprogramming.pub/how-angular-signals-solves-an-age-old-problem-ae7ec60f042f) can be modified to be suitable for our system. Maybe one `push` to determine `topoRank`-s, and a `pull` to actually...

I would love this feature so much. My Airstream/Laminar codes right now uses a lot of `split`'s, and creating dummy element for them, although worked, feel very cumbersome to me.