Confusing error message when setter is missing

If you have a property in your dao like so

 int Prop { get; }

and you try to do a Query that maps to it, an exception is raised. This is fine.
The exception which is raised though is confusing:

System.ArgumentNullException: Value cannot be null.
Parameter name: meth
   at System.Reflection.Emit.DynamicILGenerator.Emit(OpCode opcode, MethodInfo meth)
   at Dapper.SqlMapper.GetTypeDeserializerImpl(Type type, IDataReader reader, Int32 startBound, Int32 length, Boolean returnNullIfFirstMissing) in SqlMapper.cs:line 3299
   at Dapper.SqlMapper.TypeDeserializerCache.GetReader(IDataReader reader, Int32 startBound, Int32 length, Boolean returnNullIfFirstMissing) in SqlMapper.TypeDeserializerCache.cs:line 153
   at Dapper.SqlMapper.TypeDeserializerCache.GetReader(Type type, IDataReader reader, Int32 startBound, Int32 length, Boolean returnNullIfFirstMissing) in SqlMapper.TypeDeserializerCache.cs:line 50
   at Dapper.SqlMapper.GetDeserializer(Type type, IDataReader reader, Int32 startBound, Int32 length, Boolean returnNullIfFirstMissing) in SqlMapper.cs:line 1787
   at Dapper.SqlMapper.QueryAsync[T](IDbConnection cnn, Type effectiveType, CommandDefinition command) in SqlMapper.Async.cs:line 427

Can we have something more useful?

Start at GetTypeDeserializerImpl in SqlMapper.cs:line 3299, where the stack trace shows the missing setter reaches DynamicILGenerator.Emit. Reproduce the Query mapping with a DAO property declared as int Prop { get; }, then make the failure identify the missing setter or mapped property instead of raising the confusing ArgumentNullException.