v2.5.0

What's Changed

• Add overload for Either.Match that accepts a Func for neither by @Jack-Edwards in #23

Full Changelog: v2.4.0...v2.5.0

v2.4.0

What's Changed

• Add overload for DoLeftOrNeitherAsync by @Jack-Edwards in #19
• Add overload for DoLeftOrNeitherAsync by @Jack-Edwards in #20

Full Changelog: v2.3.0...v2.4.0

v2.3.0

What's Changed

• Maybe equality and EasyMonads.Core @jltrem in #15

Full Changelog: v2.2.0...v2.3.0

v2.2.0

What's Changed

• Add overload for DoLeftOrNeitherAsync by @Jack-Edwards in #13

Full Changelog: v2.1.0...v2.2.0

v2.1.0

What's Changed

• Add 'IfNoneAsync' and an overload for 'SomeOrDefault' by @Jack-Edwards in #11
• Bump version to 2.1.0 by @Jack-Edwards in #12

Full Changelog: v2.0.0...v2.1.0

v2.0.0

This release primarily enables the <nullable> attribute within the EasyMonads project. As such, I've added and updated several methods to accept nullable reference types. These added and updated methods should eliminate some warnings from consuming projects which also have the <nullable> attribute enabled.

Note, the internal behavior of both the Either and Maybe types has not changed. If a null value is provided to either type, those types will be set to their default states; Neither and None, respectively.

And to be absolutely clear, this does not add support for encapsulating nullable types, such that Maybe<int?> or Either<Unit, string?> could return null values.

v1.4.3

What's Changed

• Add overload for Maybe.Match() by @Jack-Edwards in #9

Full Changelog: v1.4.2...v1.4.3

v1.4.2

What's Changed

• Add 'SomeOrDefaultAsync' extension method for Maybe by @Jack-Edwards in #8

Full Changelog: v1.4.0...v1.4.2

v1.4.0

What's Changed

• Updates by @Jack-Edwards in #6

Full Changelog: v1.3.0...v1.4.0

v1.3.0

Increment version number