Optional
goderive
Optional | goderive | |
---|---|---|
6 | 3 | |
876 | 1,177 | |
- | - | |
0.0 | 2.8 | |
8 months ago | about 2 months ago | |
C# | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Optional
-
Nullable vs Option
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?
-
It seems like I'm forced to make this choice at least once a day
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)
-
Common C practice to avoid in C++
This library provides similar functionality to F#'s Option type. I can't vouch for it, but it's there.
-
Why GoLang supports null references if they are billion dollar mistake?
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.
-
How do you handle EF Core null return values in your projects?
You can use Optional
-
How to get rid of NullPointerException
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.
goderive
-
Do you generate Clone or Copy methods?
I found https://github.com/awalterschulze/goderive but haven't used anything like it besides mockgen
-
Why GoLang supports null references if they are billion dollar mistake?
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.
- Derives mundane Golang functions that you do not want to maintain
What are some alternatives?
language-ext - C# functional language extensions - a base class library for functional programming
go-enum - An enum generator for go
JFlepp.Maybe - A Maybe type for C#, aimed as an idiomatic port of the option type in F# to C#
goverter - Generate type-safe Go converters by simply defining an interface
Curryfy - Provides strongly typed extensions methods for C# delegates to take advantages of functional programming techniques, like currying and partial application.
gotype - Golang source code parsing, usage like reflect package
MoreLINQ - Extensions to LINQ to Objects
go-xray - Helpers for making the use of reflection easier
Optuple - .NET Standard Library for giving (bool, T) Option-like semantics
GoWrap - GoWrap is a command line tool for generating decorators for Go interfaces
NullGuard - Adds null argument checks to an assembly
generis - Versatile Go code generator.