Mismatched record type message is backwards

[jdm]

error: mismatched types: expected socket::sockaddr_basicbut found{family: int} (expected a record with field 'family' but found one with field 'sin_family')

The "expected a record with" looks like it should be the other way around, since the actual code I wrote was {family:0}.

[olsonjeffery]

I noticed this just now, as well.. was really confusing because the record in question has, like, 3 different representations because of various OS/Arch combinations. Good times.