CallMeMaybe 0.6.1

.NET Framework This package is compatible with all versions of .NET Framework. 
dotnet add package CallMeMaybe --version 0.6.1                

                    
                

            
NuGet\Install-Package CallMeMaybe -Version 0.6.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="CallMeMaybe" Version="0.6.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add CallMeMaybe --version 0.6.1                

                    
                

            
#r "nuget: CallMeMaybe, 0.6.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install CallMeMaybe as a Cake Addin
#addin nuget:?package=CallMeMaybe&version=0.6.1

// Install CallMeMaybe as a Cake Tool
#tool nuget:?package=CallMeMaybe&version=0.6.1

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.

Product Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.6.1 121 5/3/2015
0.6.0 18 5/2/2015
0.5.0 119 2/7/2015
0.4.0 99 12/29/2014
0.3.5318 218 7/25/2014
0.3.5303 88 7/9/2014
0.3.5252 175 5/20/2014
0.2.5199 96 3/28/2014
0.1.5178 66 3/7/2014

v0.6.1 - Included XML documentation
v0.6 Beta.
- Added parsers, with a couple of basic parsing extension methods.
- Added OfType<>().
- Added FirstMaybe() and SingleMaybe() extension methods.
- Added a lot of XML documentation comments.
v 0.5 Alpha. **Breaking Change**: object.Equals() override behaves differently now. Prefer `==` or `Is()` instead.
v 0.4 Alpha. Added "Is()" method, and "Values()" extension method, plus lots of comments.
v 0.3.5318 Alpha. Added better conversion to/from Nullables. Maybe IMaybe interface public. Added LINQPad sample.
v 0.3 Alpha release. Added Do() methods and an Else() overload that takes a function parameter. More correct handling of null arguments. And documentation on most of the types and methods!
v 0.2 Alpha release. API subject to change (but probably not as much as it did last time).
v 0.1 Alpha release. API subject to change.