MemoizR 0.1.0-alpha1
See the version list below for details.
dotnet add package MemoizR --version 0.1.0-alpha1
NuGet\Install-Package MemoizR -Version 0.1.0-alpha1
<PackageReference Include="MemoizR" Version="0.1.0-alpha1" />
paket add MemoizR --version 0.1.0-alpha1
#r "nuget: MemoizR, 0.1.0-alpha1"
// Install MemoizR as a Cake Addin #addin nuget:?package=MemoizR&version=0.1.0-alpha1&prerelease // Install MemoizR as a Cake Tool #tool nuget:?package=MemoizR&version=0.1.0-alpha1&prerelease
MemoizR: Simplifying Structured Concurrency in .NET
"The world is still short on languages that deal super elegantly and inherently and intuitively with concurrency" Mads Torgersen Lead Designer of C# (https://www.youtube.com/watch?v=Nuw3afaXLUc&t=4402s)
MemoizR is a powerful Structured Concurrency State implementation designed to simplify and enhance state synchronization across multiple threads in .NET applications. It offers a performant and thread-safe approach to managing concurrency challenges, making it an excellent choice for various scenarios.
Key Advantages
Simplicity and Intuitiveness: MemoizR aims to provide a straightforward and intuitive way to handle concurrency, avoiding the complexities often associated with async/await patterns (e.g. async void, .Wait, not awaiting everything and even .ConfigureAwait) in C#. It offers a more natural approach to managing asynchronous tasks and multithreading.
Scalability: This concurrency model has the potential for expansion into distributed setups, similar to the actor model. It can help you build scalable and distributed systems with ease.
Maintainable Code: MemoizR is designed to ensure the maintainability of your code, especially when dealing with challenging concurrent state synchronization problems in multi-threaded environments.
Performance Optimization: Even for simple use cases, MemoizR can optimize performance in scenarios where there are more reads than writes (thanks to memoization) or more writes than reads (using lazy evaluation).
Dynamic Lazy Memoization
With MemoizR, you can create a dependency graph that performs dynamic lazy memoization. This means that values are calculated only when needed and only if they haven't been calculated before (memoization). It also ensures efficient resource utilization and reduces unnecessary calculations (lazy). This implementation draws inspiration from the concepts found in reactively (https://github.com/modderme123/reactively)
Inspiration
MemoizR draws inspiration from various sources:
- Dynamic Lazy Memoization: (https://github.com/modderme123/reactively)
- Structured Concurrency: (https://github.com/StephenCleary/StructuredConcurrency, https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/)
Benefits
Here are some key benefits of using MemoizR:
Dependency Tracking: MemoizR automatically tracks dependencies between functions and methods, eliminating the need for manual source listing. This ensures that calculations are triggered only when necessary.
Optimization: MemoizR includes intelligent optimization algorithms. Functions are executed only if required and only once, even in complex dependency networks. This reduces unnecessary computations and enhances efficiency.
Execution Model: Push-Pull Hybrid
MemoizR utilizes a hybrid push-pull execution model. It pushes notifications of changes down the graph and executes MemoizR elements lazily on demand as they are pulled from the leaves. This approach combines the simplicity of pull systems with the execution efficiency of push systems.
Example
Here's a simple example of using MemoizR:
var f = new MemoFactory();
var v1 = f.CreateSignal(1, "v1");
var m1 = f.CreateMemoizR(async() => await v1.Get(), "m1");
var m2 = f.CreateMemoizR(async() => await v1.Get() * 2, "m2");
var m3 = f.CreateMemoizR(async() => await m1.Get() + await m2.Get(), "m3");
// Get Values
await m3.Get(); // Calculates m1 + 2 * m1 => (1 + 2 * 1) = 3
// Change
await v1.Set(2); // Setting v1 does not trigger the evaluation of the graph
await m3.Get(); // Calculates m1 + 2 * m1 => (1 + 2 * 2) = 6
await m3.Get(); // No operation, result remains 6
await v1.Set(3); // Setting v1 does not trigger the evaluation of the graph
await v1.Set(2); // Setting v1 does not trigger the evaluation of the graph
await m3.Get(); // No operation, result remains 6 (because the last time the graph was evaluated, v1 was already 2)
MemoizR can also handle scenarios where the graph is not stable at runtime, making it adaptable to changing dependencies.
var m3 = f.CreateMemoizR(async() => await v1.Get() ? await m1.Get() : await m2.Get());
Get Started with MemoizR
Start using MemoizR to simplify and optimize concurrency management in your .NET applications. Enjoy a cleaner, and more efficient approach to handling concurrency challenges.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net7.0
- MemoizR.AsyncLock (>= 0.1.0-alpha1)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on MemoizR:
Package | Downloads |
---|---|
MemoizR.Reactive
Package Description |
|
MemoizR.StructuredConcurrency
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
0.1.5 | 68 | 11/17/2024 |
0.1.4 | 120 | 5/25/2024 |
0.1.3 | 115 | 5/7/2024 |
0.1.2 | 127 | 5/6/2024 |
0.1.1 | 84 | 5/1/2024 |
0.1.1-rc.11 | 58 | 4/29/2024 |
0.1.1-rc.10 | 59 | 4/23/2024 |
0.1.1-rc.9 | 55 | 4/18/2024 |
0.1.1-rc.8 | 64 | 4/13/2024 |
0.1.1-rc.7 | 58 | 4/11/2024 |
0.1.1-rc.6 | 59 | 4/10/2024 |
0.1.1-rc.5 | 58 | 4/4/2024 |
0.1.1-rc.4 | 55 | 4/1/2024 |
0.1.1-rc.3 | 69 | 3/24/2024 |
0.1.1-rc.2 | 63 | 2/17/2024 |
0.1.1-rc.1 | 163 | 1/4/2024 |
0.1.0-rc9 | 203 | 11/6/2023 |
0.1.0-rc8 | 164 | 10/26/2023 |
0.1.0-rc7 | 140 | 10/24/2023 |
0.1.0-rc6 | 181 | 10/21/2023 |
0.1.0-rc5 | 128 | 10/19/2023 |
0.1.0-rc4 | 150 | 10/14/2023 |
0.1.0-rc3 | 141 | 10/13/2023 |
0.1.0-rc2 | 137 | 10/11/2023 |
0.1.0-rc10 | 122 | 11/12/2023 |
0.1.0-rc1 | 136 | 10/10/2023 |
0.1.0-rc.11 | 71 | 1/4/2024 |
0.1.0-alpha2 | 143 | 10/6/2023 |
0.1.0-alpha1 | 125 | 10/6/2023 |
0.0.4-rc4 | 137 | 9/24/2023 |
0.0.4-rc3 | 121 | 9/23/2023 |
0.0.4-rc2 | 121 | 9/23/2023 |
0.0.4-rc1 | 120 | 9/22/2023 |
0.0.4-beta1 | 121 | 9/21/2023 |
0.0.4-alpha1 | 118 | 9/19/2023 |
0.0.3-beta-1 | 109 | 9/15/2023 |
0.0.2-rc4 | 96 | 8/30/2023 |
0.0.2-rc3 | 105 | 8/30/2023 |
0.0.2-rc2 | 108 | 8/30/2023 |
0.0.2-rc1 | 109 | 8/30/2023 |
0.0.2-beta2 | 111 | 8/30/2023 |
0.0.2-beta1 | 120 | 8/29/2023 |
0.0.1-beta1 | 107 | 8/28/2023 |
0.0.1-alpha2 | 114 | 8/28/2023 |
0.0.1-alpha1 | 108 | 8/27/2023 |