VisualStudio 2015 and C# 6.0 are out available for preview!!

I decided that a good way to do that would be to try implement a couple of monads in C#. Monads offer a very nice way to separate core logic from the boilerplate code. They are used quite a lot in many programming languages, and in C# they are foundation for Linq. So, I was wondering how easy/hard it would be to implement them in pure C# (not with Linq) and would they end up being practical to use in a OOP language like C#?

Disclaimer: this really is a simplified and incomplete attempt – for a complete and more through take, you should go ahead and read more detailed blog posts here or here:

First, a basic intuition about monads:

monad = **data** container + some **computation** + **public interface** (‘From’ and ‘Bind’)

- Data container – in C#, simply a class
- Computation – repetitive logic that can be extracted from the main/core operation
- ‘From’ – function that wraps a value inside the monad – in C#, constructor or static factory
- ‘Bind’ – function that applies main/core operation within the context of internal computation

Lets try to implement two simple monads: Maybe (Option) and Writer monad.

Maybe monad’s internal computation checks for ‘null’ values, making top level code path clear of null checks.

Writer monad’s internal computation allows to accumulate additional information as we progress through chain of operations, hiding away explicit logging statements from the top level code path.

Code?

and here is how it is used:

You can get full source code by going to this **GitHub** page. I may continue to play around with this, potentially add other monads and more complex examples of use…