CallMeMaybe 0.3.5303

.NET Framework
There is a newer version of this package available.
See the version list below for details.
Install-Package CallMeMaybe -Version 0.3.5303
dotnet add package CallMeMaybe --version 0.3.5303
<PackageReference Include="CallMeMaybe" Version="0.3.5303" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add CallMeMaybe --version 0.3.5303
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: CallMeMaybe, 0.3.5303"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. 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.3.5303

// Install CallMeMaybe as a Cake Tool
#tool nuget:?package=CallMeMaybe&version=0.3.5303
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

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 Versions
.NET Framework net
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on CallMeMaybe:

Package Downloads
CallMeMaybe-LINQPad

Some usage samples to help you get the hang of the Maybe<> type and associated extension methods which are available in the CallMeMaybe library.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.7.1 7,395 12/31/2018
0.7.0 4,304 5/14/2018
0.6.8 1,971 10/11/2017
0.6.7 710 10/10/2017
0.6.6 805 8/31/2017
0.6.2 2,359 5/11/2016
0.6.1 1,514 5/3/2015
0.6.0 1,103 5/2/2015
0.5.0 1,711 2/7/2015
0.4.0 1,515 12/29/2014
0.3.5318 1,081 7/25/2014
0.3.5303 968 7/9/2014
0.3.5252 1,094 5/20/2014
0.2.5199 1,229 3/28/2014
0.1.5178 1,047 3/7/2014

v 0.3.5303 Alpha. Made IMaybe interface public. https://bitbucket.org/j2jensen/callmemaybe/issue/4/make-imaybe-interface-public
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.