Hiperspace.Heap
2.5.35
Prefix Reserved
dotnet add package Hiperspace.Heap --version 2.5.35
NuGet\Install-Package Hiperspace.Heap -Version 2.5.35
<PackageReference Include="Hiperspace.Heap" Version="2.5.35" />
<PackageVersion Include="Hiperspace.Heap" Version="2.5.35" />
<PackageReference Include="Hiperspace.Heap" />
paket add Hiperspace.Heap --version 2.5.35
#r "nuget: Hiperspace.Heap, 2.5.35"
#:package Hiperspace.Heap@2.5.35
#addin nuget:?package=Hiperspace.Heap&version=2.5.35
#tool nuget:?package=Hiperspace.Heap&version=2.5.35
Hiperspace.Heap
The Heap driver provides the simplest hiperspace, storing objects in the managed process heap,
it exists for testing purposes, but also for benchmark performance of other drivers.
The Heap driver uses more memory, and is slower than the Rocks driver.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. 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. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. 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. |
-
net10.0
- Hiperspace (>= 2.5.35)
- Microsoft.Bcl.HashCode (>= 6.0.0)
- protobuf-net.Core (>= 3.2.56)
- System.Numerics.Tensors (>= 10.0.3)
-
net8.0
- Hiperspace (>= 2.5.35)
- Microsoft.Bcl.HashCode (>= 6.0.0)
- protobuf-net.Core (>= 3.2.56)
- System.Numerics.Tensors (>= 10.0.3)
-
net9.0
- Hiperspace (>= 2.5.35)
- Microsoft.Bcl.HashCode (>= 6.0.0)
- protobuf-net.Core (>= 3.2.56)
- System.Numerics.Tensors (>= 10.0.3)
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 |
|---|---|---|
| 2.5.35 | 93 | 2/27/2026 |
| 2.5.33 | 98 | 2/14/2026 |
| 2.5.32 | 103 | 1/30/2026 |
| 2.5.29 | 108 | 1/17/2026 |
| 2.5.28 | 114 | 12/31/2025 |
| 2.5.26 | 196 | 12/21/2025 |
| 2.5.21 | 444 | 12/10/2025 |
| 2.5.18 | 685 | 12/3/2025 |
| 2.5.13 | 204 | 11/24/2025 |
| 2.5.8 | 187 | 11/15/2025 |
| 2.5.2 | 220 | 11/6/2025 |
| 2.5.0 | 215 | 10/20/2025 |
| 2.4.6 | 208 | 9/23/2025 |
| 2.4.4 | 298 | 8/7/2025 |
| 2.4.2 | 186 | 7/28/2025 |
| 2.4.0 | 220 | 7/10/2025 |
| 2.3.8 | 201 | 7/1/2025 |
| 2.3.7 | 213 | 6/18/2025 |
| 2.3.3 | 223 | 6/5/2025 |
| 2.2.2 | 230 | 5/5/2025 |
https://www.cepheis.com/hiperspace/20260227
# Overview
## Cube Enhancements
A minor enhancement has been made to fully qualify references to **Hiperspace.Functions**. This prevents naming conflicts when a domain also uses **Functions**.
When one of a Cube’s **Dimensions** is `Node`, the `Node` view is added to the Cube along with `Edge` definitions that represent navigation between the **Dimension** and the Cube. In this release, the naming of these edges has been updated to ensure consistent navigation through a HiperGraph, using a common TypeName convention:
* TypeName `Cube:Drilldown` for navigation from a *Dimension* to the *Cube*.
* TypeName `Cube:Dimension` for navigation from the *Cube* to a *Dimension*.
### Example
In the [Cube Example](https://github.com/channell/Hiperspace/blob/master/examples/Cube/Cube.hilang) ***Customer Sector*** and ***Product*** are *Dimensions* that can also be viewed as `Nodes`. The ***Contract Cube*** therefore has `Node` and `Edges` added as a views because.
[image]blogs/Blogs/Butterfly/product-model.png[/image]
* ***Contact*** (*Cube*) has one ***Account*** and ***Account*** has one ***Customer*** and ***Customer*** has one ***Sector*** (*Dimension*), it is inferred that ***Sector*** is a *Dimension* of *Cube* ***Contact***.
* ***Contact*** (*Cube*) has one ***Instrument*** and ***Instrument*** has one ***Product***, it is inferred that ***Product*** is a *Dimension* of *Cube* ***Contract***.
When viewed through a **HiperGraph** the *Cube* becomes a `Node` that links ***Sector*** *node* to ***Product*** *Node*
If you *drilldown* from ***Product*** to ***Contact_Cube*** and *drilldown* to ***Sector***, the shortest *HiperEdge* from ***Product*** to ***Sector*** is through the ***Contract_Cube*** slice that summarizes the connection between the two `Nodes`. We call this combination of *HiperGraph* and *Cube* "*HiperCube*", and is useful for **AI** prompts like *"which sector uses most widgets?"*
[image]blogs/Blogs/Butterfly/product-graph.png[/image]