http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I now your pain, earlier this week, I've been trying to come up with nicer, and more strongly typed ways to cope with events in Rhino.Mocks (strongly typed EventRaiser, event subscribtion and verification) and I failed miserably. I think I just gave up (at least for now). You can see the attempts at my blog. And BTW, why are delegates so limited in cooperation with generics? :/ It's just annoying http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment8http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment8Fri, 21 Mar 2008 07:05:37 GMTExecute((t, k) => Bar(t, k)); Execute((t, k) => Foo(t, k)); http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment7http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment7Thu, 20 Mar 2008 18:26:47 GMTLet me also say that they could have enabled this for very simple scenarios such as the one you are dealing with. In the blog post by Eric Lippert referenced above he basically says that they could have done it in certain scenarios, but in other scenarios it would have been impossible. He said that they didn't want two different inference algorithms that produce slightly different results. While I am certainly not a compiler writer, that sounds like they are taking an idealistic approach and not a pragmatic one. The pragmatic approach would have been to try and make type inference work in as many different scenarios as possible, and have it fail when the resolution is unreachable. http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment6http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment6Thu, 20 Mar 2008 12:23:38 GMTIf you swap the bool on the end to Func<T, K, bool> then everything except for Execute(Bar) and Execute(Foo) works. And I agree with Frans, I have heard all the explanations about why it wouldn't work, but I wish they could have found a way to make it work. http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment5http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment5Thu, 20 Mar 2008 12:06:22 GMTYes, this is pretty annoying. I ran into this as well when I wanted to introduce some types for prefetchpath specifications inside linq queries and wanted to get rid of the explicit generic argument specifications... IMHO it's a compiler flaw, no matter how many excuses they invent: they introduced syntactic sugar, then make the compiler deal with that in all cases. http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment4http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment4Thu, 20 Mar 2008 08:39:18 GMTLambda stuff is nice but I would love to see Boo DSL for rhino mocks :) http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment3http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment3Thu, 20 Mar 2008 07:55:50 GMTpublic static void Execute<T, K>(Func<bool, T, K> e) should be public static void Execute<T, K>(Func<T, K,bool> e) :) after that there will be errors only with Execute(Bar); Execute(Foo); you can rewrite this as Action<int, string> bar_ptr = Bar; Execute(bar_ptr); // compiles fine Func<int, string, bool> foo_ptr = Foo; Execute(foo_ptr);// compiles fine Here is big explanation why type inference didn't work in this case: http://blogs.msdn.com/ericlippert/archive/2007/11/05/c-3-0-return-type-inference-does-not-work-on-member-groups.aspx But for me that was not very convincing. http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment2http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment2Thu, 20 Mar 2008 07:22:58 GMTMaybe you were looking for Func<T, K, bool>? http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment1http://ayende.com/3199/csc-exe-and-delegate-inference-or-why-c-has-awkward-syntax#comment1Thu, 20 Mar 2008 07:02:27 GMT