I have a suggestion that I hope dapper writers will take it seriously and implement it.

1.Dapper does not support mapping of anonymous types well and has serious bugs
2.The advantage of anonymity, I don't have to say much about it.
3.What about his relationship with Dapper?
Example1
I have a type Student (id, age, sex, sid) and a school (sid, sname)。
I get the (id, age, sname) of these two types by connecting queries, but I don't want to define a new type.

public List<TResult> Query<TResult> Query(Func<T1,T2,TResult> fun,string sql)
{
     return connection.Query<TResult>(sql);
}

I have defined the following methods, which can be solved

var list = Query((stu,sch)=>new 
{
stu.Id,
stu.Age,
sch.sname
},"select id,age,sname from student join school on student.sid=school.sid")

Start with the generic Query entry point shown in the issue and review how Dapper currently maps joined SQL results. The requested outcome is support for projecting joined Student and school data into an anonymous result without defining a new type; existing mapping behavior and tests would need to establish the scope.