Home/ Questions/Q 818605
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T02:10:41+00:00

This is a bit of a strange one but I’ve just seen something on

  • 0

This is a bit of a strange one but I’ve just seen something on twitter which kind of baffled me and I’m interested to know more.

Rob Conery tweeted the following a couple of hours ago: Class name of the day: “Maybe<T>“. Method of the day: “ToMaybe<T>()“. He then went on to offer a Tekpub coupon to anyone who could guess where it came from. He linked to a further tweet which had a clue and from that I worked out that it was Entity Framework Code-Only but while trying to determine the usage someone else answered to which Rob replied …EF CodeOnly – dealing with uncertainty….

So my question boils down to what exactly is he referring to with uncertainty and how does this fit in to Entity Framework Code-Only?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Maybe<T> is one of typical monads, see e.g. this Wikipedia example. Monads are widely used in functional programming: you definitely know IEnumerable<T>, which is monad as well. The LINQ itelf is sometimes described as “language integrated monads”. Few more links:

    Presence of Maybe<T> shows that code quality of the Entity Framework definitely isn’t bad: they use well-known concept there, which is described many many times (I suspect there is no ToMaybe<T>() there – there must be ToMaybe<T>(T value) and Nothing, so it is just a Rob’s mistake).

    • 0