Optional VS goderive

Since then C# introduced nullable which takes away some of the needs for a Option type. So what is your opionion? Do libraries like Optional still have a place when nullable is enabled?

Optional is my go-to for c# (you could also use the F# Option of course but pulling fsharp.core into a C# project tends to raise eyebrows in my experience)

This library provides similar functionality to F#'s Option type. I can't vouch for it, but it's there.

Not really. C# doesn't have monads but you can easily add something like https://github.com/nlkl/Optional which is great for a team familiar with option types and IMO will lead to a more productive team with a more concise code base.

You can use Optional

The option type is a different way to represent an optional value. This type asks if a value exists and, if so, accesses the value. When trying to access the value which doesn’t exist, it raises an exception. This solves the problem of NullPointerException raised in code areas away from the bug. In Java there is the Optional class. In C# (until C# 7 ) there is the Nullable type which is only for value types but you can create your own or use a library.

I found https://github.com/awalterschulze/goderive but haven't used anything like it besides mockgen

Now, am I going to do the same with a library like goderive just so I can use FP techniques to get, amongst some other things, less nil checks? No. Probably not. If I wanted to use primarily FP techniques in my code, I would probably be using something else in the first place. Go isn't a great environment for guaranteeing immutability for starters, so anything like that is necessarily going to be an incomplete experience. And in the bargain, my code would, in my opinion at least, be less readable and maintainable.