Hoàng
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.
[Vyukov](https://www.1024cores.net/home/lock-free-algorithms/queues/non-intrusive-mpsc-node-based-queue) already mentioned this, and [Jiffy](https://arxiv.org/abs/2010.14189) has already shown an example of it. I just want to clarify the blocking scenario that can occur in this implementation: Given 3 threads:...
@kyri-petrou I think in today system, "block indefinitely" a thread is quite unlikely to happen, because this must be either: 1. Block by user bad code: every lock-freedom systems suffer...
/attempt #1004 Options Cancel my attempt
I'm currently trying to implement the first approach. The implementation is basically what you've highlighted: create `methodCodeHashSignatures` for JavaModule, and move from there. I did some adjustment to call graph...