2023/08/17/parse-dont-validate-and-other-type-safety-driven-shenanigans-plus-a-csharp-wishlist/ #96
Replies: 3 comments 2 replies
|
Awesome post. Got a bit confused with the language-ext part tbh since I hadn't had any experience in the past with anything like that, but it does start looking better the longer you look at it 😁 |
0 replies
|
Have you tried my OneOf library? It's a much smaller library than LanguageExt as it's just for unions, but it does support Try methods as well as switch and match |
1 reply
|
Great example! I've been meaning to look into |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
2023/08/17/parse-dont-validate-and-other-type-safety-driven-shenanigans-plus-a-csharp-wishlist/
Making use of the type system is something I feel should be important when working in a strongly typed language like C#. However, I don’t feel like that’s the case, and I would love for the language to push folks in the direction of creating more robust programs, where the compiler provides more help in proving the correctness of the code.
https://blog.codingmilitia.com/2023/08/17/parse-dont-validate-and-other-type-safety-driven-shenanigans-plus-a-csharp-wishlist/
All reactions