Marc Gravell

Dapper's current behaviour is to skip over nulls, rather than actively assign. A case can be made for either behaviour, and I can totally get behind making this configurable -...

All the deep. There *are* some ways of configuring this, but honestly: in most cases it is more pragmatic just to: ``` new { obj.Foo, obj.Bar, obj.Blap } ``` to...

I'm going to refer to the Apache license to answer that: > Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides...

> and why it was splitted in the first place. to avoid the overhead of an extra async state-machine per entry > The exception seems to arise when the pair.Command...

Dammit! Fixing - brainfart

@michal-ciechan > if you want to use the AOT aspects of it, but there is a bug in a specific method call that it is replacing, can we easily switch...

@Tornhoof > Clean aot only version and then think about interceptors for later migration of existing Code. Right; to explain - there is a secondary API which the generators use...

@giammin > I expected DapperAOT to be a complete api rewrite with no compatibility/interoperability with the ref-emit version. Happy to over-deliver :)

@T-Gro > will not work in non-C# projects such as F#. Those compilers will not understand the interception Yes, I'm very conscious of that. And to be clear, I'm not...

@T-Gro I should also emphasize: even if there is no "interceptors" metaphor that would allow (some language) to use the regular Dapper API: the secondary API is - well, honestly...