language-ext
Optional
Our great sponsors
language-ext | Optional | |
---|---|---|
41 | 6 | |
6,159 | 875 | |
- | - | |
6.9 | 0.0 | |
4 days ago | 8 months ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
language-ext
-
The Monad Invasion - Part 2: Monads in Action!
You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).
-
The Monad Invasion - Part 1: What's a Monad?
Language-Ext is my personal favourite, but it can be a bit overwhelming for beginners due to its extensive feature set
- Why don't you just use F#?
-
The combined power of F# and C#
> but I just want something closer to Scala, but for .Net
That's what I'm working toward with my language-ext library [1]. Obviously more support for expression based programming would be welcome (and higher kinds), but you can do a lot with LINQ and a good integrated library surface.
[1] https://github.com/louthy/language-ext
-
Option<T> monad for Unity/UniTask
Definitely a fan of option types, I wonder this library has anything over the C# library language-ext which also has an Option type?
-
Result pattern: language-ext vs FunctionalExtensions?
Hey, I am considering adopting the Result pattern in my codebase. Wanted to get some opinions from someone who has experience with it: should I start with language-ext or FunctionalExtensions?
-
John Carmack on Functional Programming in C++ (2018)
> [1] https://github.com/louthy/language-ext
Cool library. I've had a few of these patterns in my Sasa library for years, but you've taken it to the Haskell extreme! Probably further than most C# developers could stomach. ;-)
You might be interested in checking out the hash array mapped trie from Sasa [1]. It cleverly exploits the CLR's reified generics to unbox the trie at various levels which ends up saving quite a bit of space and indirections, so it performs almost on par with the mutable dictionary.
I had an earlier version that used an outer struct to ensure it's never null, similar to how your collections seem to work, but switched to classes to make it more idiomatic in C#.
I recently started sketching out a Haskell-like generic "Deriving" source generator, contrasted with your domain-specific piecemeal approach, ie. [Record], [Reader], etc. Did you ever try that approach?
[1] https://sourceforge.net/p/sasa/code/ci/default/tree/Sasa.Col...
[2] https://sourceforge.net/p/sasa/code/ci/57417faec5ed442224a0f...
-
Don't sleep on Linq query syntax if you regularly iterate through large/complex data sources
languageext supports linq for its monads and I kinda love it. The challenge is convincing my colleagues. 😅
-
What C# feature blew your mind when you learned it?
language-ext supports it and it's pretty dang cool.
-
It's actually not that bad...
I can only recommend c# language extensions library https://github.com/louthy/language-ext
Optional
-
Nullable vs Option
Since then C# introduced nullable which takes away some of the needs for a Option type. So what is your opionion? Do libraries like Optional still have a place when nullable is enabled?
-
It seems like I'm forced to make this choice at least once a day
Optional is my go-to for c# (you could also use the F# Option of course but pulling fsharp.core into a C# project tends to raise eyebrows in my experience)
-
Common C practice to avoid in C++
This library provides similar functionality to F#'s Option type. I can't vouch for it, but it's there.
-
Why GoLang supports null references if they are billion dollar mistake?
Not really. C# doesn't have monads but you can easily add something like https://github.com/nlkl/Optional which is great for a team familiar with option types and IMO will lead to a more productive team with a more concise code base.
-
How do you handle EF Core null return values in your projects?
You can use Optional
-
How to get rid of NullPointerException
The option type is a different way to represent an optional value. This type asks if a value exists and, if so, accesses the value. When trying to access the value which doesn’t exist, it raises an exception. This solves the problem of NullPointerException raised in code areas away from the bug. In Java there is the Optional class. In C# (until C# 7 ) there is the Nullable type which is only for value types but you can create your own or use a library.
What are some alternatives?
OneOf - Easy to use F#-like ~discriminated~ unions for C# with exhaustive compile time matching
JFlepp.Maybe - A Maybe type for C#, aimed as an idiomatic port of the option type in F# to C#
CSharpFunctionalExtensions - Functional extensions for C#
Curryfy - Provides strongly typed extensions methods for C# delegates to take advantages of functional programming techniques, like currying and partial application.
MoreLINQ - Extensions to LINQ to Objects
Optuple - .NET Standard Library for giving (bool, T) Option-like semantics
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
NullGuard - Adds null argument checks to an assembly
csharplang - The official repo for the design of the C# programming language
FParsec.CSharp - A thin C# wrapper for FParsec.