3 ms·
> Yeah, though, one annoyance with Nullable<T> in C# is that T must be a value type. Unnecessary because class types already allow null. I would not be surpris
by SideburnsOfDoom 9y ago
> Yeah, though, one annoyance with Nullable<T> in C# is that T must be a value type.
Unnecessary because class types already allow null. I would not be surprised if a method e.g. public Customer TryFindCustomer(int id); returns null if it can't find the customer.
Of course, if you want to return either a customer or an error details, then you need another type or generic wrapper.
- bunderbunder 9y agoNot strictly necessary, no. But the example I wrote was getting at was meant to point out that this bifurcation can make it harder to compose generic types. It's not really an ideal design decision for modern C# so much as a hold-over from the language's early years, when idiomatic usage favored a much more imperative style of programming.