Add support for Future() with the new Linq provider

Very good point, the impl has changed.

Oren,

I was referring to the ToFuture and ToFutureValue methods:

public static IEnumerable<T> ToFuture<T>(this IEnumerable<T> query)
{
var nhQueryable = query as NhQueryable<T>;
if (nhQueryable == null)
throw new NotSupportedException("You can also use the AsFuture() method on NhQueryable");

They can return IEnumerable<T>, no problem there, but they should take IQueryable<T>, since they only support a NhQueryable<T> as a parameter anyway.

Otherwise, you'll see the extension methods even in strings or any other enumerable, i.e. "Yada Yada".ToFuture() will compile.

Diego,

Because if I would implement them on IQueryable, they wouldn't be executed.

Consider:

var people = s.Query<Person>().AsFuture(); <-- on queryable

var users = s.Query<User>().AsFuture(); <-- on queryable

people.ToList(); <-- users never had the chance to execute the AsFuture()!

I'm curious, why did you implement the extension methods on IEnumerable<T> instead of IQueryable<T>?

You can now use: ToFuture() and ToFutureValue() extension methods in order to use future values from NHibernate.