[matt-edmondson]

Requested by Matt · project thread

Fixes #301.

Before: a record that declared operator == or operator != did not compile in C# or in Rust. C# reported CS0111, because a record already synthesises both operators and the comparison-partner logic added whichever one was missing. Rust reported E0119, because the record derived PartialEq beside the declared impl PartialEq.

After: both targets compile. In C#, a record's declared == or != is written down as inexpressible, since the record supplies both, and no partner is added for it. In Rust, a record that declares == leaves PartialEq out of its derive, so the declared impl is the only one. Records that declare no equality operator keep their current output.

How: CSharpGenerator checks whether an operator is one a record synthesises over its own type (RecordSynthesises) before writing it, and MissingComparisonPartners skips those. RustGenerator drops PartialEq from the derive list when the record declares ==. RecordEqualityTests compiles a record declaring == and one declaring only != with dotnet build and rustc, and pins the unchanged output for a plain record.

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
7 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud