SwiftCollections is a high-performance collection library for performance-sensitive .NET workloads, including game systems, simulations, and spatial queries.
- Optimized for Performance: Designed for low time complexity and minimal memory allocations.
- Framework Agnostic : Works with .NET, Unity, and other game engines.
- Full Serialization Support: Out-of-the-box round-trip serialization via MemoryPack across most core collections, with System.Text.Json constructor support on .NET 8+. A Lean (no MemoryPack) variant is available for projects that manage serialization independently.
- Fast core collections:
SwiftDictionary,SwiftHashSet,SwiftList,SwiftQueue,SwiftStack,SwiftSortedList - Specialized containers:
SwiftBucket,SwiftGenerationalBucket,SwiftPackedSet,SwiftSparseMap,SwiftBiDictionary - Flat 2D/3D storage:
SwiftArray2D,SwiftArray3D,SwiftBoolArray2D,SwiftShortArray2D - Pools:
SwiftObjectPool,SwiftArrayPool,SwiftCollectionPool, and typed pool helpers - Observable collections for change-tracking scenarios
- Spatial queries via typed
SwiftBVH<TKey, TVolume>,SwiftSpatialHash<TKey, TVolume>, andSwiftOctree<TKey, TVolume>plus default numerics wrappers - Lightweight diagnostics via
SwiftCollections.Diagnosticsfor opt-in low-level log/event routing
-
Choose the package that fits your runtime:
- Use
SwiftCollectionsif you want the standard package with built-inMemoryPacksupport. - Use
SwiftCollections.Leanif you want the same collections without theMemoryPackdependency, such as when integrating with toolchains that do better without MemoryPack-generated code. - Use
SwiftCollections.FixedMathSharpif you need fixed-point spatial query volumes backed byFixedMathSharp, withMemoryPacksupport included. - Use
SwiftCollections.FixedMathSharp.Leanif you need the fixed-point companion without theMemoryPackdependency.
- Use
-
Install via NuGet:
-
Standard package:
dotnet add package SwiftCollections
-
Lean (no MemoryPack) package:
dotnet add package SwiftCollections.Lean
-
Fixed-point companion (with MemoryPack):
dotnet add package SwiftCollections.FixedMathSharp
-
Fixed-point companion, Lean (no MemoryPack):
dotnet add package SwiftCollections.FixedMathSharp.Lean
-
-
Or Download/Clone:
git clone https://github.com/mrdav30/SwiftCollections.git
Then reference
src/SwiftCollections/SwiftCollections.csprojor build the package locally.
SwiftCollections is published in two build variants per package so you can choose between convenience and maximum compatibility:
SwiftCollections/SwiftCollections.FixedMathSharpIncludesMemoryPackand its generated serialization support. This is the best default choice for most .NET applications.SwiftCollections.Lean/SwiftCollections.FixedMathSharp.LeanExcludes theMemoryPackpackage and uses internal shim attributes so the same source compiles without the dependency. Choose this when you do not need built-in MemoryPack serialization, when you prefer to use a different serializer, or when your target environment is sensitive to MemoryPack-generated code paths.
Both standard and lean variants expose the same core collections API. The main difference is whether MemoryPack is part of the package and serialization surface.
If you use Unity Burst AOT, prefer the Lean variants. MemoryPack's Unity support is centered on IL2CPP via its .NET Source Generator path, so the Lean variants are the safer choice for Burst AOT scenarios.
Unity support is maintained separately:
- Core package dependency: MemoryPack (standard variants only)
- Optional fixed-point companion: FixedMathSharp via
SwiftCollections.FixedMathSharporSwiftCollections.FixedMathSharp.Lean
- SwiftDictionary: A high-performance dictionary optimized for O(1) operations and minimal memory usage.
- SwiftBiDictionary: A bidirectional dictionary for efficient forward and reverse lookups in O(1).
- SwiftHashSet: An optimized set for unique values with fast operations.
- SwiftBucket: High-performance collection for O(1) addition and removal with stable indexing.
- SwiftGenerationalBucket: A bucket variant that tracks generations to prevent stale references.
- SwiftPackedSet: A compact set implementation for dense integer keys.
- SwiftSparseMap: A memory-efficient map for sparse key distributions.
- SwiftQueue: Circular-buffer-based queue for ultra-low-latency operations.
- SwiftList: A dynamic list optimized for speed-critical applications.
- SwiftSortedList: Dynamically sorted collection with O(log n) operations.
- SwiftStack: Fast array-based stack with O(1) operations.
- SwiftArray2D / SwiftArray3D: Efficient, flat-mapped arrays for 2D and 3D data.
- SwiftBVH: Bounding Volume Hierarchy for broad-phase spatial queries.
- SwiftSpatialHash: Spatial hash for high-churn, uniform-size, and sparse huge-world scenes.
- SwiftOctree: Hierarchical octree for dynamic scenes with uneven density.
SwiftDictionary<TKey, TValue> and SwiftHashSet<T> use deterministic default comparers for string keys when no comparer is supplied. object keys also get a SwiftCollections default comparer that hashes strings deterministically, but non-string object-key determinism still depends on the underlying key type. Custom comparers are still supported.
- SwiftObjectPool: Thread-safe generic object pooling for improved memory usage and performance.
- SwiftArrayPool: Array-specific pool for efficient reuse of arrays.
- SwiftCollectionPool: Pool for reusable collection instances (e.g., List, HashSet).
- Default Collection Pools: Ready-to-use pools are available for
SwiftList,SwiftQueue,SwiftHashSet,SwiftDictionary,SwiftStack,SwiftPackedSet, andSwiftSparseMap.
- SwiftBVH: Bounding Volume Hierarchy for broad-phase queries with mixed or extreme object-size variance.
- SwiftSpatialHash: Spatial hash for sparse huge-world needle queries and uniform-size high-churn workloads.
- SwiftOctree: Hierarchical octree for dynamic scenes, uneven density, and repeated region queries.
Use them by workload:
- SwiftBVH is the best fit for scenes with mixed or extreme object-size variance (e.g. tiny units alongside large terrain pieces), large churning objects, and general broad-phase intersection queries over heterogeneous populations. It is not thread-safe; synchronize access externally if needed. Avoid it for dense same-size clustered scenes and for sparse huge-world needle (tiny query window) lookups.
- SwiftSpatialHash is the best fit for sparse, huge-world scenes where small query windows rarely overlap many cells (O(1) bucket lookup dominates), and for high-frequency updates with mostly uniform-size objects. Performance degrades when object sizes vary widely, since a fixed cell size becomes either too coarse or too fine.
- SwiftOctree is the strongest all-around performer for dynamic scenes with uniform or small objects, mixed broad-phase, and repeated regional queries over uneven distributions. Prefer it when most objects are similar in size or when queries target specific spatial sub-regions repeatedly.
- SwiftObservableArray / SwiftObservableList / SwiftObservableDictionary: Reactive, observable collections with property and collection change notifications.
- DiagnosticChannel / DiagnosticEvent / DiagnosticLevel: Lightweight diagnostics primitives for routing informational, warning, or error events without coupling the library to a higher-level logging framework.
- SwiftCollectionDiagnostics.Shared: Ready-to-use shared channel for library-wide diagnostics.
Diagnostics are opt-in and disabled by default until you configure a minimum level and sink.
var bvh = new SwiftBVH<int>(100);
var volume = new BoundVolume(new Vector3(0, 0, 0), new Vector3(1, 1, 1));
bvh.Insert(1, volume);
var results = new SwiftList<int>();
bvh.Query(new BoundVolume(new Vector3(0, 0, 0), new Vector3(2, 2, 2)), results);
Console.WriteLine(results.Count); // Output: 1var typedBvh = new SwiftBVH<int, BoundVolume>(100);
typedBvh.Insert(1, new BoundVolume(new Vector3(0, 0, 0), new Vector3(1, 1, 1)));var spatialHash = new SwiftSpatialHash<int>(64, 2f);
spatialHash.Insert(1, new BoundVolume(new Vector3(0, 0, 0), new Vector3(1, 1, 1)));
var nearby = new List<int>();
spatialHash.QueryNeighborhood(
new BoundVolume(new Vector3(0, 0, 0), new Vector3(1, 1, 1)),
nearby);var worldBounds = new BoundVolume(new Vector3(0, 0, 0), new Vector3(64, 64, 64));
var octree = new SwiftOctree<int>(
worldBounds,
new SwiftOctreeOptions(maxDepth: 6, nodeCapacity: 8),
minNodeSize: 1f);
octree.Insert(1, new BoundVolume(new Vector3(2, 2, 2), new Vector3(4, 4, 4)));
var visible = new List<int>();
octree.Query(new BoundVolume(new Vector3(0, 0, 0), new Vector3(8, 8, 8)), visible);var fixedBvh = new SwiftFixedBVH<int>(100);
fixedBvh.Insert(1, new FixedBoundVolume(new Vector3d(0, 0, 0), new Vector3d(1, 1, 1)));var array2D = new SwiftArray2D<int>(10, 10);
array2D[3, 4] = 42;
Console.WriteLine(array2D[3, 4]); // Output: 42var queue = new SwiftQueue<int>(10);
queue.Enqueue(5);
Console.WriteLine(queue.Dequeue()); // Output: 5var array = new int[10].Populate(() => new Random().Next(1, 100));using System;
using SwiftCollections.Diagnostics;
DiagnosticChannel diagnostics = SwiftCollectionDiagnostics.Shared;
diagnostics.MinimumLevel = DiagnosticLevel.Warning;
diagnostics.Sink = static (in DiagnosticEvent diagnostic) =>
{
Console.WriteLine($"[{diagnostic.Channel}] {diagnostic.Level}: {diagnostic.Message} ({diagnostic.Source})");
};
diagnostics.Write(DiagnosticLevel.Info, "Skipped because the minimum level is Warning.", "Bootstrap");
diagnostics.Write(DiagnosticLevel.Error, "Pool allocation failed.", "Bootstrap");Build the solution:
dotnet build SwiftCollections.slnx -c DebugRun the unit tests:
dotnet test tests/SwiftCollections.Tests/SwiftCollections.Tests.csproj -c Debug --no-buildRun benchmarks:
dotnet run --project tests/SwiftCollections.Benchmarks/SwiftCollections.Benchmarks.csproj -c Release -f net8Useful benchmark runner commands:
dotnet run --project tests/SwiftCollections.Benchmarks/SwiftCollections.Benchmarks.csproj -c Release -f net8 -- list
dotnet run --project tests/SwiftCollections.Benchmarks/SwiftCollections.Benchmarks.csproj -c Release -f net8 -- dictionary
dotnet run --project tests/SwiftCollections.Benchmarks/SwiftCollections.Benchmarks.csproj -c Release -f net8 -- query --list flat
dotnet run --project tests/SwiftCollections.Benchmarks/SwiftCollections.Benchmarks.csproj -c Release -f net8 -- hashset --filter "*Contains*"
dotnet run --project tests/SwiftCollections.Benchmarks/SwiftCollections.Benchmarks.csproj -c Release -f net8 -- all --list flatWith no extra arguments, BenchmarkDotNet's default switcher behavior is used. Leading non-option arguments are treated as benchmark selection aliases, and any remaining arguments are forwarded to BenchmarkDotNet.
netstandard2.1net8.0- Windows, Linux, and macOS
Fixed-point BVH support is provided by the separate SwiftCollections.FixedMathSharp companion package.
We welcome contributions! Please see our CONTRIBUTING guide for details on how to propose changes, report issues, and interact with the community.
- mrdav30 - Lead Developer
- Contributions are welcome! Feel free to submit pull requests or report issues.
For questions, discussions, or general support, join the official Discord community:
For bug reports or feature requests, please open an issue in this repository.
We welcome feedback, contributors, and community discussion across all projects.
This project is licensed under the MIT License.
See the following files for details:
- LICENSE β standard MIT license
- NOTICE β additional terms regarding project branding and redistribution
- COPYRIGHT β authorship information