this post was submitted on 16 Jun 2023
2 points (100.0% liked)
C Sharp
1526 readers
1 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've found C# nullable types quite frustrating, because nullable generics don't work properly when they can be instantiated with both value types and reference types.
It feels like a very hacky approximation of an option type, which we are now probably stuck with. Compared to all the other amazing features they've added, that one felt a bit half baked.
To be honest I feel the same way about it now.