Missing implicit numeric cast of decimal to integer in C# record

Hi, I've found that Dapper behaves differently when using plain classes or records (working on Oracle 12).

When getting results from a command, like

return await connection.QueryAsync<SomeObject>(query);

this

public class SomeObject
{
    public int Id { get; set; }
}

works fine while this

public record SomeObject(int Id)

throws

System.InvalidOperationException: A parameterless default constructor or one matching signature (System.Decimal ID) is required for SomeNamespace.SomeObjectmaterialization

If I change property data type, like this

public record SomeObject(decimal Id)

it works, but I don't want to use decimal instead of int.

Start with the QueryAsync reproduction in the issue and compare materialization of the class and positional record when the result value is System.Decimal. Done means a record with an int Id can be materialized from that result, while the existing class behavior remains intact.