this post was submitted on 10 Aug 2024

17 points (94.7% liked)

C Sharp

1526 readers

1 users here now

A community about the C# programming language

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

c/dotnet

founded 1 year ago

MODERATORS

Ategon@programming.dev

nibblebit@programming.dev

Spyros@programming.dev

17

Option Result library for c# (programming.dev)

submitted 3 months ago* (last edited 3 months ago) by DrDeadCrash@programming.dev to c/csharp@programming.dev

13 comments fedilink hide all child comments

A collection of tools for dealing with nulls, failures and the generic type issues that arise in this domain.

https://github.com/Andy3432344/SafeResults

I'm the author, let me know what you think!

*Edit: updated to show GitHub link, sorry!

you are viewing a single comment's thread
view the rest of the comments

[–] kogasa@programming.dev 3 points 3 months ago (1 children)

Null pointers are one thing, C# nulls (with nullable reference types enabled) are another. They behave a lot like an Option monad with the caveat that the static analysis can technically be tricked by incorrect hints.

[–] DrDeadCrash@programming.dev 2 points 3 months ago

I very much disagree with this, Null Reference Exceptions have been a huge problem in c#. Nullable reference types are a partial fix, but the question of "how do I 'return' an error from a statically typed method" is not answered there.