Just a few questions

[fedeAlterio]

Why opt for a fresh implementation instead of contributing to the existing R3/R3Async repositories? R3 already represents a modern reimplementation that addresses essentially all the limitations of classic Rx.NET, so it might have been a natural place natural place for further improvements or performance optimizations.

Regarding naming, “Signals” in the UI ecosystem is generally associated with automatic dependency tracking (for example, Angular, React or JS frameworks or in my own SignalsDotnet project), though I’m not entirely convinced that applies in this case.

One additional point: I noticed that SignalAsync implementation appear to draw inspiration from R3Async. A brief acknowledgment of that influence would likely not make a significant difference for the project itself, but it would have made a meaningful difference for me, since the implementation is not trivial, and it took some time.

Also, I noticed the use of ConfigureAwait(false). I don't Think this is a good choice, for reason I explained in R3Async readme, but I would love to talk about that further 🙂