Rx.NET
dotty-cps-async
Our great sponsors
Rx.NET | dotty-cps-async | |
---|---|---|
61 | 10 | |
6,474 | 170 | |
1.3% | - | |
6.6 | 9.4 | |
25 days ago | 10 days ago | |
C# | Scala | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Rx.NET
-
Cool features like Random.Shared
One of the greatest things i discovered recently, is Reactive programming / Reactive Extensions ( https://github.com/dotnet/reactive ).
-
Patterns for consuming a throttled/rate limited external APIs?
https://github.com/dotnet/reactive has a lot of different time related extensions for "events". Maybe you'll find something for yourself, if you google for rate limiting with reactive.
- [Game Dev] Programmation réactive fonctionnelle (FRP) pour les jeux?
-
How can you detect when a user has stopped scrolling with WPF
Install Reactive Extensions: https://github.com/dotnet/reactive
-
What is your preferred asynchronous programming library?
Another option is to use the RxJava library in Java. This library uses reactive programming principles to make it easy to write asynchronous and event-driven code. It's particularly well-suited for handling streams of data and allows you to write code that is both efficient and easy to read.
-
MVVM Question: How do you manage the interaction between Model and ViewModel?
I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.
- Understanding the full benefits of yield and use of IAsyncEnumerable
- The 1st Alpha Release of System.Reactive.Async now on NuGet
-
Async Methods after setting a property.
If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.
-
System.Reactive v6.0.0-preview.1 available on NuGet
We'd really appreciate if it consumers of the library could update and provide any issues / bugs via the GitHub repo: https://github.com/dotnet/reactive/issues
dotty-cps-async
-
Help a Kotlin convert back into Scala world
Now in scala we have direct mode transformers: dotty-cps-async [https://github.com/rssh/dotty-cps-async] with cps-async-connect [https://github.com/rssh/cps-async-connect ] supports all well-knowm monad stacks, for ZIO also exists ZIO-direct [https://github.com/zio/zio-direct ] , for IO - cats-effect-cps [https://github.com/typelevel/cats-effect-cps ], for kyo [https://github.com/fwbrasil/kyo ] - kyo-direct.
-
dotty-cps-async 0.9.12 is out
dotty-cps-async: https://github.com/rssh/dotty-cps-async
-
The case against Effect Systems (e.g., the IO data type)
Hmm, you can write direct-style code with monad: https://github.com/rssh/dotty-cps-async allows this, exists support libraries exist for near all well-known effect systems: https://github.com/rssh/cps-async-connect, so you can use async/await with IO/ZIO the same as with Future. Although in IO style, any operation that mutates state is async, it's hard to write code where you should place `await` near each line. And it looks like automatic coloring is a too radical change of concepts for most functional programmers. The option to allow using <- in the direct style may be more popular, but this requires changes to the scala core. Another question - are we need effective systems to be present in each program in industrial-style development? Here I agree that mostly no.
- dotty-cps-async 0.9.11 is out. (bugfixes and experimental loom support)
- dotty-cps-async 0.9.9
- New Scala 3 Codebases
- Also dotty-cps-async 0.9.8 with scala-native support
- dotty-cps-async 0.9.8 with scala-native support
-
Dotty-cps-async 0.9.7 is released.
This is a generic async/await transformer for scala3 which allows using effectful monads in the direct style. URL: (https://github.com/rssh/dotty-cps-async )
-
Language-assisted Flattening
dotty-cps-async [rssh/dotty-cps-async ] with automatic coloring do something very similar in two steps. Automatic coloring defines implicit conversion F[A] => A as x => await(x)(m). The compiler inserts those awaits inside async blocks and then eliminates them later via cps-transform. Exists some limitations which we need to add for effect monads like IO (we don't want run effect twice and don't want to screw semantics of effects by extra memoizing). So, if your language has a possibility to implement effect monads, then you need a possibility to restrict using Flattenable.
What are some alternatives?
Dynamic Data - Reactive collections based on Rx.Net
scala3-example-project - An example sbt project that compiles using Dotty
RxJS - A reactive programming library for JavaScript
cps-async-connect
ObservableComputations - Cross-platform .NET library for computations whose arguments and results are objects that implement INotifyPropertyChanged and INotifyCollectionChanged (ObservableCollection) interfaces.
scala-3-migration-guide - The Scala 3 migration guide for everyone.
duckdb - DuckDB is an in-process SQL OLAP Database Management System
scala-gopher - Implementation of CSP constructions (Communication Sequence Process, i.e. go-like channels) in scala
Disruptor-cpp - Port of LMAX Disruptor to C++
libretto - Declarative concurrency and stream processing library for Scala
MediatR - Simple, unambitious mediator implementation in .NET
dedav4s - Declarative Data Viz 4 Scala