Maybe Just Nothing
Yet another variation of the good old Maybe monad with eager execution written in Dart.
Creating maybe-values
Internally, Maybe is an abstract class with two implementations: Just and Nothing.
The most common scenario is probably discarding null from nullable values:
int? nullableValue;
final val = Just(nullableValue).type<int>();
final doubled = val.map((x) => x * 2);
doubled.ifPresent(print);
Nullable values can also be wrapped in Just:
int? nullableValue;
final val = Just(nullableValue);
final justNull = Maybe(null);
The Nothing value may be created either typed or untyped:
final nothing1 = Nothing();
final nothing2 = Nothing<int>();
final nothing3 = Nothing<String?>();
You may even distinguish between presence and absence of nulls themselves:
Maybe<void> yay = Just(null);
Maybe<void> nay = Nothing<void>();
Mapping values
Mapping means transformation of the wrapped value by applying a function.
Since Maybe itself is immutable, mapping operations do not actually modify the value.
Instead, they always return another Maybe.
Just(2).map((x) => x * 2).ifPresent(print);
If the mapping function also returns a Maybe, use flatMap():
Maybe<int> triple(int x) => Just(x).map((x) => x * 3);
Just(2).flatMap(triple).ifPresent(print);
An operation on two maybe-values can be performed using merge():
final two = Just(2);
final three = Just(3);
two.merge(three, (x, y) => x + y).ifPresent(print);
Filtering values
Filtering is checking whether the maybe-value satisfies a certain condition. If it does,
the value remains intact, otherwise Nothing is returned.
To filter by the value itself, use the where():
Just(2).where((x) => x.isEven).ifPresent(print);
Just(3).where((x) => x.isEven).ifPresent(print);
To filter by type, use type<T>():
final maybeInt = Just(2).type<int>();
final maybeString = Just(2).type<String>();
Fallback chain
The chain() method implements the Chain of Responsibility design pattern. It accepts another
maybe-value of the same type. If the current value is Nothing, the next value in the chain gets returned.
Another way to implement the same idea is to use the fallback() method. It accepts a "fallback"
function which returns another maybe-value of the same type. If the current value is Nothing,
this fallback function will be called and its result will be returned. You can provide several fallback functions.
They will be called in sequence until a Just value is received.
Nothing<int>()
.chain(Nothing<int>())
.chain(Just(2))
.chain(Just(3))
.ifPresent(print);
Nothing<int>()
.fallback(() => Nothing<int>())
.fallback(() => Just(2))
.fallback(() => Just(3))
.ifPresent(print);
Consuming the value
The intention of Maybe is to give it the consumer function instead of retrieving the value.
This is the most concise and clear way of using it.
Maybe a;
a
..ifPresent(print)
..ifNothing(() {});
Reading the value
Sometimes, however, you need the actual value. In such cases you'll have to provide the default value as well.
In the simplest scenario, use or():
Maybe<int> a;
final value = a.or(0);
final valueFromFuture = await a.orAsync(Future.value(0));
A provider function can be specified instead of the default value:
Maybe<int> a;
final value = a.orGet(() => 0);
final valueFromFuture = await a.orGetAsync(() async => 0);
If there is no default value, an exception can be thrown:
Maybe<int> a;
final value = a.orThrow(() => 'Oops!');
In some rare cases, it can be convenient to check for emptiness directly:
Maybe<int> myInt;
if (myInt is Just<int>) {
print(myInt.value);
}
if (myInt is Nothing) {
print('The value is missing');
}