https://github.com/gui-cs/nstack

New Stack - Explorations on Unicode, IO, new idioms and error handling for .NET
https://github.com/gui-cs/nstack

cross-platform csharp dotnet runes strings text unicode

Last synced: 4 days ago
JSON representation

New Stack - Explorations on Unicode, IO, new idioms and error handling for .NET

• Host: GitHub
• URL: https://github.com/gui-cs/nstack
• Owner: gui-cs
• License: bsd-3-clause
• Created: 2017-05-12T06:53:08.000Z (over 7 years ago)
• Default Branch: develop
• Last Pushed: 2024-01-22T13:51:28.000Z (10 months ago)
• Last Synced: 2024-09-18T05:32:21.193Z (about 2 months ago)
• Topics: cross-platform, csharp, dotnet, runes, strings, text, unicode
• Language: C#
• Homepage:
• Size: 1.34 MB
• Stars: 124
• Watchers: 8
• Forks: 26
• Open Issues: 24
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
# NStack

![Build](https://github.com/gui-cs/NStack/actions/workflows/build.yml/badge.svg)

[![Version](https://img.shields.io/nuget/v/NStack.Core.svg)](https://www.nuget.org/packages/NStack.Core)

[![Downloads](https://img.shields.io/nuget/dt/NStack.Core)](https://www.nuget.org/packages/NStack.Core)

[![License](https://img.shields.io/github/license/gui-cs/NStack.svg)](LICENSE)

![Bugs](https://img.shields.io/github/issues/gui-cs/NStack)

NOTE: NStack has moved to the [gui-cs org](https://github.com/orgs/gui-cs/).

Currently, this library contains a port of the Go string, and Go rune support as well as other Unicode helper methods.

You can browse the [API documentation](https://gui-cs.github.io/NStack).

Install the [NuGet package from NuGet.org](https://www.nuget.org/packages/NStack.Core) by installing `NStack.Core`.

# Future Additions

The long term goal is to make this module an exploration of what the .NET APIs for IO looked like if they only

used exceptions for either invalid parameters being passed to

methods and used results/error codes for most IO operations:

* Exceptions have a role, but IO code tends to become ugly in its presence.

* Other areas include making an IO layer that does not surface "string" for

filenames, as in Unix there are really no filenames as we treat them in

.NET, but rather file names are a collection of bytes, which do not necessarily

can be decoded into UTF8 [1].  

To make things simple, this assumes that UTF8 strings (ustring in this code)

can exist without them being valid UTF8 strings, but rather a collection of bytes.

[1] For example, older file systems can have filenames that made sense with

a particular character set and are effectively not possible to map into strings.