News for hackers. Stuff that matters.
Re:Don't return null; use a tail call by troygoode on Tuesday January 10, 2012 @09:44AM (#3447070)
C# offers this via Nullable<T>:

  Nullable<int> someNumber = foo.TryAndGetSomeNumber();
  if(someNumber && someNumber.HasValue)
    doSomething( someNumber.Value );
Re:Don't return null; use a tail call by dkersten on Tuesday January 10, 2012 @12:02PM (#3447746)
if(someNumber && someNumber.HasValue)

You still have to remember to do this check. Will the compiler complain if you use someNumber.Value without checking that its valid first? If not, then its not really the same thing.

The point of Haskell's Maybe is that the compiler will make sure that you take both cases (that there is a value and that there isn't a value) into account (because to extract the value you must pattern match and pattern matches must be exhaustive, otherwise you get a compile error).

Re:Don't return null; use a tail call by chc on Tuesday January 10, 2012 @02:44PM (#3448633)
Eh, that's putting it a little too strongly. Haskell is a nice language, but it still doesn't protect you from all your mistakes. The easiest way to extract the value in Haskell is fromJust, which simply errors if no value was returned. I do agree that Haskell makes it more natural, though.
Re:Don't return null; use a tail call by troygoode on Tuesday January 10, 2012 @08:17PM (#3450010)
The compiler won't, no - but many/most developers use static analysis tools like ReSharper which WILL tell you that you have a possible NullReferenceException there if you don't check it.
Re:Don't return null; use a tail call by bmm6o on Tuesday January 10, 2012 @04:10PM (#3449031)
More idiomatic C# might be:

  int result;
  if (foo.TryAndGetSomeNumber(out result))
    doSomething(result);
There might also be a foo.GetSomeNumber() that returns an int or throws on failure.

[fixed formatting]

Re:Don't return null; use a tail call by troygoode on Tuesday January 10, 2012 @08:18PM (#3450014)
I disagree that your example is more idiomatic. Maybe pre-3.0...
Re:Don't return null; use a tail call by arethuza on Tuesday January 10, 2012 @09:53AM (#3447103)
Why don't you use int? rather than Nullable<int> - aren't they equivalent?
Re:Don't return null; use a tail call by lallysingh on Tuesday January 10, 2012 @09:58AM (#3447117)
The point is, all values of the int are available. Null is stored somewhere outside the underlying int.
Re:Don't return null; use a tail call by arethuza on Tuesday January 10, 2012 @10:04AM (#3447144)
It was just a question about the syntax used - why type Nullable<int> when there is direct syntactical support in C# for nullable types - in this case you could simply type int? rather than Nullable<int>
Re:Don't return null; use a tail call by endianswap on Tuesday January 10, 2012 @11:14AM (#3447455)
At the very least Nullable<T> is a lot friendlier to search than T? if you want to learn more on the subject.
Re:Don't return null; use a tail call by bfung on Tuesday January 10, 2012 @01:57PM (#3448387)
not everyone is familiar with C#, and Nullable<int> conveys better meaning in writing to that kind of audience.
Re:Don't return null; use a tail call by troygoode on Tuesday January 10, 2012 @10:39AM (#3447268)
int? is syntactic sugar for Nullable<int>, which didn't seem worth getting into :-)