Lazily.R3 0.7.0

dotnet add package Lazily.R3 --version 0.7.0
                    
NuGet\Install-Package Lazily.R3 -Version 0.7.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Lazily.R3" Version="0.7.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Lazily.R3" Version="0.7.0" />
                    
Directory.Packages.props
<PackageReference Include="Lazily.R3" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Lazily.R3 --version 0.7.0
                    
#r "nuget: Lazily.R3, 0.7.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Lazily.R3@0.7.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Lazily.R3&version=0.7.0
                    
Install as a Cake Addin
#tool nuget:?package=Lazily.R3&version=0.7.0
                    
Install as a Cake Tool

R3 adapter

Lazily.R3 is an optional net10.0 package. The core Lazily assembly has no R3 dependency.

Lazily to R3

Context.ToR3State is cold: each subscription owns one Effect, emits the current value, tracks dynamic dependencies, suppresses equal values, and detaches its edges when disposed. ToSharedR3State is explicit sharing: one owned effect feeds a one-value ReplaySubject.

An R3 error is recoverable (OnErrorResume) and does not tear down the effect. Disposing a shared bridge completes its current subscribers. Lazily batching may collapse intermediate state values, so this is a state projection, not a lossless event-stream adapter.

R3 to Lazily

Context.BindR3State requires same-thread ingress. ThreadSafeContext.BindR3State serializes cross-thread ingress through the context lock. Both return an equality-guarded Source<T> and an owned subscription. R3 errors update LastError and remain recoverable; R3 completion is terminal and recorded in Completion. Disposal unsubscribes but leaves the last state readable. Reentrant writes follow the underlying Context/ThreadSafeContext semantics, and Batch coalescing remains a Lazily concern.

Performance

benchmarks/Lazily.R3.Benchmarks permanently compares native Lazily, native R3, and both bridge directions under BenchmarkDotNet's memory diagnoser. Profiling before budgets were introduced observed 488 B/update. A later short run on .NET 10.0.10 observed 336 B/update for native Lazily and both bridge directions (native R3 allocated 0 B/update). These are environment-specific profiling observations, not budgets. Set budgets only after repeated runs on stable hardware and allocation source profiling.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • net10.0

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.7.0 0 10/5/2026
0.6.0 60 9/29/2026
0.5.0 95 9/3/2026