SamSaffron/dapper-dot-net — pull request #21 by paultyng (2012-01-19 22:08:04+00:00)
Title: Dynamic parameters and overload resolution

Per [Issue #81](http://code.google.com/p/dapper-dot-net/issues/detail?id=81) on Google Code.

I see the remarks about the odd dynamic parameters to work around VS completion, but in trying to customize the library for my own use (see [issue #80](http://code.google.com/p/dapper-dot-net/issues/detail?id=80)) I was having problems with the dynamic typed parameters because they cause runtime overload resolution instead of compile time resolution ([relevant MSDN article](http://msdn.microsoft.com/en-us/library/dd264736.aspx)).

> Overload resolution occurs at run time instead of at compile time if one or more of the arguments in a method call have the type dynamic, or if the receiver of the method call is of type dynamic.

Seems like this may pose a performance or other issue and not be desirable. I understand the frustrations with anonymous types in VS and the autocompletion, its very annoying, but is it worth runtime overload resolution? For my specific needs I had to remove this, and in case anyone else finds this useful, here is the pull.