From 57abddc13f30ba7b9fd8502f975b8bcb34fe3ab2 Mon Sep 17 00:00:00 2001 From: Yoshifumi Kawai <46207+neuecc@users.noreply.github.com> Date: Mon, 29 Jul 2024 16:23:24 +0900 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 52d5f485..713b1432 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ The new future of [dotnet/reactive](https://github.com/dotnet/reactive/) and [Un I have over 10 years of experience with Rx, experience in implementing a custom Rx runtime ([UniRx](https://github.com/neuecc/UniRx)) for game engine, and experience in implementing an asynchronous runtime ([UniTask](https://github.com/Cysharp/UniTask/)) for game engine. Based on those experiences, I came to believe that there is a need to implement a new Reactive Extensions for .NET, one that reflects modern C# and returns to the core values of Rx. -* Stopping the pipeline at OnError is a billion-dollar mistake. +* Stopping the pipeline at OnError is a mistake. * IScheduler is the root of poor performance. * Frame-based operations, a missing feature in Rx, are especially important in game engines. * Single asynchronous operations should be entirely left to async/await. @@ -2239,4 +2239,4 @@ Similar to `IObservable`, if you want to stop the stream when an `OnErrorResu License --- -This library is under the MIT License. \ No newline at end of file +This library is under the MIT License.