Found 288 packages
Option types for C# with LINQ support and rich fluent syntax for many popular uses: var maybeOne = "one".ToMaybe(); Maybe<string> maybeAnother; var maybeBoth = from one in maybeOne from another in maybeAnother select one + another; maybeBoth.Match( both => Console.WriteLine("Result is: {0}", both), @else: () => Console.WriteLine("Result is Nothing, as one of the inputs was Nothing") );
CSharpFunctionalExtensions - functional extensions for C#
Maybe is monads implementation for .NET
Option types for C# with LINQ support and rich fluent syntax for many popular uses: var maybeOne = "one".ToMaybe(); Maybe<string> maybeAnother; var maybeBoth = from one in maybeOne from another in maybeAnother select one + another; maybeBoth.Match( both => Console.WriteLine("Result is: {0}", both), @else: () => Console.WriteLine("Result is Nothing, as one of the inputs was Nothing") );
Optional is a robust option/maybe type for C#.
Maybe/Optional monad implementation for C#. For more information see http://csharp-functional.readthedocs.io/en/latest/maybe-monad.html.
Maybe.NET is a library of probabilistic data structures. Instantly start using bloom filters, skip lists, count min sketch, and more!
Package Description
Binaries for the Option type. Visit https://github.com/tejacques/Option for an overview and usage examples.
An extension with Just() method for Functional.Maybe
Maybe monad for C# - to handle null values and exceptions better - including Linq support, chaining, and asynchronous programming.
An option type for .NET.
Option types for C# with LINQ support and rich fluent syntax
Functional Option for .net
Provides a class and a few extension methods to facilitate common operations with values that may or may not exist. Traditionally, programmers often use `null` references to represent values that "aren't there", but the problem is that this was never their intended purpose. - Languages like C# don't provide a way to differentiate between reference variables that can be null and those that are guaranteed not to be. - The inventor of null references has [apologized](http://en.wikipedia.org/wiki/Tony_Hoare#Quotations) for creating them in the first place, calling them his "billion-dollar mistake." - This misuse of null references has spread far and wide, leading to the unfortunately-named `Nullable<>` type (which, being a value type, is never actually null), and attributes like `[CanBeNull]` and `[NotNull]` to help programmers know when they can expect a method to treat a null value as legitimate input. All this leaves us in a position where our best hope of avoiding `NullReferenceException`s lies in trying to make sure that our reference variables are *never* null. But in that case, how do we indicate when a value is *optional*? Well, that's where `Maybe<>` comes in.
Async extensions for Nils Lück's Optional library.
An utility library that helps avoiding nulls.
C# implementation of the Maybe (optional value) wrapper with fluent and LINQ APIs.
Helper methods for writing unit tests using Maybe types.
SoftwareCraft.Maybe represents the OOP implementation of a functional concept. Instead of returning null, return a Maybe, and the code will be much cleaner and the intent much clearer.