Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/stirlinglabs/collections.net

Collections used throughout the Stirling Labs C# codebase
https://github.com/stirlinglabs/collections.net

async collections data-types dotnet key-value

Last synced: about 12 hours ago
JSON representation

Collections used throughout the Stirling Labs C# codebase

Host: GitHub
URL: https://github.com/stirlinglabs/collections.net
Owner: StirlingLabs
License: mit
Created: 2021-09-08T14:18:46.000Z (about 3 years ago)
Default Branch: main
Last Pushed: 2022-12-21T08:12:48.000Z (almost 2 years ago)
Last Synced: 2024-11-04T21:45:39.850Z (16 days ago)
Topics: async, collections, data-types, dotnet, key-value
Language: C#
Homepage:
Size: 364 KB
Stars: 2
Watchers: 5
Forks: 2
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE.txt

Awesome Lists containing this project

README

        ![Collections.Net](https://raw.githubusercontent.com/StirlingLabs/Collections.Net/main/utilities-collections.jpg)

Collections used in the Stirling Labs codebase that aren't in the standard libraries.

## 🚀 How to install

```bash

> dotnet add PROJECT package StirlingLabs.Utilities.Collections

```

## 👀 What's included

Any collection datatype implementation code that is used in more than one package is a contender to be included here. If you see something that you think should be included, please

[create an issue](/StirlingLabs/Collections.Net/issues/new) or PR so we can discuss it.

## 🐣 Lifecycle

This should be the first place that common code is generalised. If it turns out that the implementation should be separated for some reason (licensing or some other optimisation) then it should be fully moved to the new package and then included back here via NuGet.  Users of Utilities.Net should not have to change their code during this process (if namespaces absolutely *have* to be modified, provide aliases).

If the reason for separating a module out ends, it should be *moved* back into Utilities as soon as it can be safely achieved (and the unecessary repo archived).  At no point should there be two code repositories being maintained; a single source of truth must exist at all times.